linux-kernel - Re: [PATCH 15/28] kgdb,docs: Update the kgdb docs to include kdb

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4B7C3C56.8040801@windriver.com>
Date:	Wed, 17 Feb 2010 12:58:30 -0600
From:	Jason Wessel <jason.wessel@...driver.com>
To:	Randy Dunlap <rdunlap@...otime.net>
CC:	linux-kernel@...r.kernel.org, kgdb-bugreport@...ts.sourceforge.net,
	mingo@...e.hu
Subject: Re: [PATCH 15/28] kgdb,docs: Update the kgdb docs to include kdb

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/