Remote gdb broken in -CURRENT?
From: Greg 'groggy' Lehey (grog_at_FreeBSD.org)
Date: 10/30/04
- Previous message: Robert Watson: "Re: panic in pipes"
- Next in thread: Ryan Sommers: "Re: Remote gdb broken in -CURRENT?"
- Reply: Ryan Sommers: "Re: Remote gdb broken in -CURRENT?"
- Maybe reply: Frank Mayhar: "Re: Remote gdb broken in -CURRENT?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 30 Oct 2004 11:55:31 +0200 To: FreeBSD current users <FreeBSD-current@FreeBSD.ORG>
Is anybody currently using remote gdb kernel debugging in -CURRENT? I
tried yesterday (embarrassingly, during my kernel debug tutorial), and
it looks as if things are broken.
Specifically, I was doing it in conjunction with firewire. The kernel
was built with 'options GDB', and it showed that the corresponding gdb
functions were included, but the sysctl debug.kdb.available shows only
ddb. I did a bit of looking around for what might have caused it, but
wasn't successful.
Any ideas?
Greg
-- See complete headers for address and phone numbers _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Robert Watson: "Re: panic in pipes"
- Next in thread: Ryan Sommers: "Re: Remote gdb broken in -CURRENT?"
- Reply: Ryan Sommers: "Re: Remote gdb broken in -CURRENT?"
- Maybe reply: Frank Mayhar: "Re: Remote gdb broken in -CURRENT?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|