Message-ID: <4B7C3C56.8040801@windriver.com>
Date: Wed, 17 Feb 2010 12:58:30 -0600
From: Jason Wessel <jason.wessel@windriver.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Randy Dunlap <rdunlap@xenotime.net>
CC: linux-kernel@vger.kernel.org, kgdb-bugreport@lists.sourceforge.net,
       mingo@elte.hu
Subject: Re: [PATCH 15/28] kgdb,docs: Update the kgdb docs to include kdb
References: <1266014143-29444-1-git-send-email-jason.wessel@windriver.com> <1266014143-29444-16-git-send-email-jason.wessel@windriver.com> <4B7700B0.1030402@xenotime.net>
In-Reply-To: <4B7700B0.1030402@xenotime.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 987
Lines: 34

Randy Dunlap wrote:
> On 02/12/10 14:35, Jason Wessel wrote:
>> +	kgdbwait	[KGDB] Stop kernel execution and enter the
>> +			kernel debugger at the earliest opportunity if
>> +			kgdb was configured on as a boot argument.
> 
> What does "kgdb was configured on as a boot argument" mean?
> 

Changed to:

-- 
	kgdbwait	[KGDB] Stop kernel execution and enter the
			kernel debugger at the earliest opportunity.
--


We'll assume someone actually configured the kernel debugger with
ekgdboc, kgdboc, or kgdbdbgp.  The previous text was attempting to
indicate that kgdbwait only does something when you also configure a
kgdb I/O driver.

Where it stops varies on how early the I/O driver and architecture
trap processing is available.

Jason.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/