[Resending to get wider coverage]

All,

While there are ways to work around some of the problems that Greg
describes, the simple fact is that kernel debugging has gone downhill
quite badly in the past year.  Much of this decay appears to be due
to the rush to get GDB 6.x imported in time for FreeBSD 5.3.  I thank
Marcel profusely for working on this, but more work is needed.  I'm
looking for volunteers to spend a few evenings digging into GDB, KDB,
and DDB and working out as many issues as possible.  Greg's email
should serve as a good starting point for these tasks.

Thanks,

Scott

Greg 'groggy' Lehey wrote:
In the last 10 months, I've had continual problems trying to use gdb
for kernel debugging.  I'm currently revising my notes for the BSDCan
tutorial, and I can't work out how to get it to work any more.  Since
about June of last year I've discovered:

- I can no longer get a dump out of ddb with the 'panic' command.  I
  need to 'call doadump'

- 'panic' doesn't only not do a dump, it doesn't reset the system
  either.  I need to press 'reset'.

- The invocation to do kernel debugging with gdb keeps changing.  A
  year ago, it was simple: 'gdb -k kernel dump'.  Now the -k command
  is gone, and on what I believe to be a valid kernel dump, kgdb gives
  me:

# kgdb kernel.debug /var/crash/vmcore.1 kgdb: cannot read PTD

- It's possible that the dump isn't valid after all, of course. But I
can't debug the local system via /dev/mem either:


  # kgdb kernel.debug /dev/mem
  [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined 
symbol "ps_pglobal_lookup"]

  (kgdb) bt
  #0  0x00000000 in ?? ()

- Firewire debugging no longer works if you haven't compiled firewire
  into the kernel.  Given the bugs I've seen above, I can't be
  bothered to try building a kernel with firewire, since I don't have
  much expectation that it will work either way.

So what gives?  Has the gdb interface withered away due to lack of
love?  Do *you* use it?  If so, how do you address the issues above?

Greg
--
See complete headers for address and phone numbers.


_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to