lkml.org 
[lkml]   [2004]   [Feb]   [13]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateFri, 13 Feb 2004 12:04:53 -0700
FromTom Rini <>
SubjectRe: [PATCH][0/6] A different KGDB stub
On Fri, Feb 13, 2004 at 10:58:38AM -0800, Chris Wright wrote:

> * Tom Rini (trini@kernel.crashing.org) wrote:
> > On Wed, Feb 11, 2004 at 04:27:56PM -0800, Andrew Morton wrote:
> > > CONFIG_KGDB_SYSRQ		(Just turn it on by default?)
> > > 
> > > I have never used (or, as far as I know, needed) any of the above.
> > 
> > I think CONFIG_KGDB_SYSRQ can die since with the 8250 and enet drivers
> > you can try and connect at any point, which will schedule a breakpoint
> > and you can get in like that.  As for NO_KGDB_CPUS, I'm not entirely
> > certain why this can't go away and there'd be an array of NR_CPUS in
> > size.
> 
> Using kgdboe I've had numerous times where it gets a bit wedged and
> only sysrq-g could get the breakpoint.

Alright.   We can just always have it on SYSRQ+KGDB then.

-- 
Tom Rini
http://gate.crashing.org/~trini/
-
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/

\
 
 \ /
  Last update: 2005-03-22 14:00    [from the cache]
©2003-2008