On Thu, Jun 15, 2006 at 03:27:40AM +0200, Andi Kleen wrote: > On Wed, Jun 14, 2006 at 04:47:58PM -0700, Tom Rini wrote: > > > Then all of our stuff should be #ifdef KGDB; while merging from 2.6.12 > > > to 2.6.13 I recall it noticing a few of the #ifdef KGDB's had been > > > removed. > > > > Yes, there really shouldn't be any #ifdef KGDB's in the kernel tree and > > we're down to very few[1] and I think it's really just one in the end > > we'll need. > > That was __might_sleep()? I'm still dubious about that one. It might > be possible to just change the caller. Do you have a full backtrace > for it?
No, that one I suspect, but haven't had a chance to verify, can die. The one we can't get rid of is our adding a flag for pidhash_init() being done. The problem is that many GDB front-ends (Eclipse) will always do an 'info threads' upon connect. But if they connect before pidhash_init() is done, we need to 'fake' the information rather than try and dig up the real info. -- Tom Rini _______________________________________________ Kgdb-bugreport mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
