Re: Remote gdb broken in -CURRENT?
From: Ryan Sommers (ryans_at_gamersimpact.com)
Date: 10/30/04
- Previous message: Gary Jennejohn: "Re: EHCI considered harmful?"
- In reply to: Greg 'groggy' Lehey: "Remote gdb broken in -CURRENT?"
- Next in thread: Greg 'groggy' Lehey: "Re: Remote gdb broken in -CURRENT?"
- Reply: Greg 'groggy' Lehey: "Re: Remote gdb broken in -CURRENT?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 30 Oct 2004 08:06:29 -0500 To: Greg 'groggy' Lehey <grog@FreeBSD.org>
Greg 'groggy' Lehey wrote:
>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?
>
>
This is probably caused by you not having any serial ports flagged for
GDB. In /boot/device.hints look for the 'hint.sio.X.flags' where X is
your serial port. It should be 0x90 for remote GDB debugging.
-- Ryan Sommers ryans@gamersimpact.com _______________________________________________ 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: Gary Jennejohn: "Re: EHCI considered harmful?"
- In reply to: Greg 'groggy' Lehey: "Remote gdb broken in -CURRENT?"
- Next in thread: Greg 'groggy' Lehey: "Re: Remote gdb broken in -CURRENT?"
- Reply: Greg 'groggy' Lehey: "Re: Remote gdb broken in -CURRENT?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|