Re: Remote gdb broken in -CURRENT?

From: Tai-hwa Liang (avatar_at_mmlab.cse.yzu.edu.tw)
Date: 10/31/04

  • Next message: Alexander Leidinger: "Re: EHCI considered harmful?" 
    Date: Sun, 31 Oct 2004 20:55:50 +0800 (CST)
To: Greg 'groggy' Lehey <grog@FreeBSD.org>

    On Sun, 31 Oct 2004, Greg 'groggy' Lehey wrote:
    > On Saturday, 30 October 2004 at 8:06:29 -0500, Ryan Sommers wrote:
    >> 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.
    >
    > You shouldn't need any. As I said, this is with firewire.
    >
    >> 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.
    >
    > To select this serial port for both remote gdb and serial console,
    > yes. I did check this and found it to be 0x10 (only serial console).
    > This has not stopped gdb from working on my older -CURRENT (6 months
    > or so) machine.
    >
    > It's possible that you're right, but that would be a recent bug.
    > Unfortunately, we were trying this on the machine of a course
    > participant, and he's no longer available. I'll check your suggestion
    > when I get back home in a week or so.
    >
    > Is anybody currently using remote gdb (serial or firewire) on a
    > -CURRENT built in the last few weeks? If so, did you need to do
    > anything special to get it to run?

       I can't get remote gdb works with firewire since the new KDB framework
    was imported. If I remembered correctly, someone was asked the similar
    question about on the list a couple of months ago, and the answer is
    simply: It's broken, use serial port instead.
    _______________________________________________
    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"

  • Next message: Alexander Leidinger: "Re: EHCI considered harmful?"

    Relevant Pages

    • Re: Remote gdb broken in -CURRENT?
      ... > Greg 'groggy' Lehey wrote: ... >> was built with 'options GDB', and it showed that the corresponding gdb ... It should be 0x90 for remote GDB debugging. ... To select this serial port for both remote gdb and serial console, ...
      (freebsd-current)
    • Re: Remote gdb broken in -CURRENT?
      ... > I can't get remote gdb works with firewire since the new KDB framework ... It's broken, use serial port instead. ...
      (freebsd-current)
    • Re: KGDB connection failure - Please help, Im desparate! (=> or desperate)
      ... I've modified remote.c in gdb to print the data coming across the ... Can anyone think of a reason why the target isn't outputting debug packets to ... the serial port? ... Ignoring packet error, continuing... ...
      (freebsd-questions)
    • Re: sys_write() racy for multi-threaded append?
      ... sometimes easier to have on gdb per processor if you can get your brain ... What do you do, fire up the target ... gdbstubs/kgdbstubs is kernel side so you boot the two cores and each core ... serial port, the other uses a different one. ...
      (Linux-Kernel)
    • Re: Inspiron 1525 Hardware
      ... console if remote console was needed. ... You need a 'real' serial port for console, ... Firewire is an alternative which won't work for a different reason: ... for Genesis Software - http://www.gsoft.com.au ...
      (freebsd-stable)