On Thu, 2006-10-05 at 08:46 -0700, George Anzinger wrote: > Tom Rini wrote: > > On Wed, Oct 04, 2006 at 08:42:04PM -0700, Piet Delaney wrote: > > > > > >>Ton, George, Amit, et. al: > >> > >>If CONFIG_KGDB isn't defined, the kernel should be exactly the > >>same as when kgdb isn't integrated. So shouldn't we should add > >>#ifdef CONFIG_KGDB in the traps.c code where the traps are > >>initialized and panic notify is registered. > > > > > > No, because that makes the code look way too ugly. If there's no harm > > in doing something if kgdb is or isn't compiled in, we want to do it, > > such as in this case. > > > For what its worth, I a) agree with Piet, and b) disagree with active init of > the traps. In the last version of kgdb I built I coded a static init of the > trap notify. The value used was conditionally defined in a kgdb header file > thus resulting in clean trap.c code.
Where is the "static init of the trap notify" that your refering to? > > This enabled kgdb to come up earlier than the running of the init code (other > things may be required...) Sounds like the right approach. > -- Piet Delaney Phone: (408) 200-5256 Blue Lane Technologies Fax: (408) 200-5299 10450 Bubb Rd. Cupertino, Ca. 95014 Email: [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Kgdb-bugreport mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
