Re: Looking for FreeBSD kernel debugging help
On Wed, 11 Jun 2003, Nat Lanza wrote: > On Wed, 2003-06-11 at 06:22, Terry Lambert wrote: > > Someone should port the network debugging from Darwin using > > the tiny IP stack from NetBSD. > > Well, there's this: > > http://ipgdb.sourceforge.net/ > > > IPGDB is a collection of extensions to GDB and FreeBSD-4.3 > > to allow two-machine kernel debugging over UDP. It behaves > > much like two-machine kernel debugging over serial ports. > > > > These extensions can easily be applied to other releases of > > FreeBSD. With a little bit of modification, these extension > > can be applied to other BSD variants. > > It hasn't been updated in a while, but it's definitely a start. It works > pretty well for 4.3, and I know it's been updated to work with 4.6 > (though possibly not in the sourceforge distribution). I think that Groggy was working on this a while back. Regards - Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, sharpe[at]ethereal.com, http://www.richardsharpe.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for FreeBSD kernel debugging help
On Wed, 2003-06-11 at 06:22, Terry Lambert wrote: > Someone should port the network debugging from Darwin using > the tiny IP stack from NetBSD. Well, there's this: http://ipgdb.sourceforge.net/ > IPGDB is a collection of extensions to GDB and FreeBSD-4.3 > to allow two-machine kernel debugging over UDP. It behaves > much like two-machine kernel debugging over serial ports. > > These extensions can easily be applied to other releases of > FreeBSD. With a little bit of modification, these extension > can be applied to other BSD variants. It hasn't been updated in a while, but it's definitely a start. It works pretty well for 4.3, and I know it's been updated to work with 4.6 (though possibly not in the sourceforge distribution). --nat ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for FreeBSD kernel debugging help
Daniel O'Connor wrote: > Serial GDB is very nice.. You can even do firewire debugging, but I guess you > guys can't really use that :) > (Firewire mini-PCI board? 8-) Someone should port the network debugging from Darwin using the tiny IP stack from NetBSD. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for FreeBSD kernel debugging help
On Wed, 11 Jun 2003 18:22, Soren Kristensen wrote: > Lesson learned: > > Advanced FreeBSD documentation sucks if you're not a kernel hacker, but > remote kernel debugging works great and are actually kinda fun Procedural things are more likely to be usefully documented in the handbook or FAQ (or The Complete FreeBSD), rather than a specific man page. They can be a bit stale though :( Serial GDB is very nice.. You can even do firewire debugging, but I guess you guys can't really use that :) (Firewire mini-PCI board? 8-) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for FreeBSD kernel debugging help
Hi Everybody, First, thanks to everybody offering tips and help. The good news is that the problem is solved. I couldn't wait, so I finally decided to learn a little FreeBSD kernel debugging. After reading lots of not very comprehensive man pages and other guides, I got a 4.4 kernel compiled with ddb and set up remote debugging over the 2nd serial port with gdb. Again, after reading even more on using gdb, I set a bunch of breakpoints a did a little tracing and got the problem localized to a PCI configuration problem, probably a undocumented hardware bug in the Geode SC1100 processor combined with not very smart PCI config code in FreeBSD. I have patched FreeBSD to boot on the net4801 board, more details after I know exactly what's the issue is. Lesson learned: Advanced FreeBSD documentation sucks if you're not a kernel hacker, but remote kernel debugging works great and are actually kinda fun Regards, Soren Kristensen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
