Missing a step in new(er) Remote gdb/kdb setup?

From: Lonnie VanZandt (lonnie.vanzandt_at_ngc.com)
Date: 08/04/05

  • Next message: Hanspeter Roth: "Unabel to resurrect your old /etc/x" 
    To: freebsd-current@freebsd.org
Date: Thu, 4 Aug 2005 09:35:34 -0600

    Marcel Moolenaar - or anyone who has properly setup the new remote
    gdb/kdb,

           You are, I believe, the programmer for the revised remote kernel debug
    interface in FreeBSD 5.4. If so, perhaps you could advise me on why I might
    be receiving a "Ignoring packet error, continuing..." at startup from a
    command like:

           kgdb -r /dev/cuaa0 /tmp/kernel.debug

    I have verified that I have 9600 8N1 connectivity between the host and
    the target and have observed the opening handshake of the remote gdb
    protocol being sent from the host. I know the cable and the sios are ok
    because I verified that a getty login over the link worked find.

    I have worked with remote kernel debugging on other systems and even on
    FreeBSD in the 5.2.1 release prior to the gdb -k to kgdb switchover. So, I
    think I'm doing the right steps but perhaps something else has changed?

    I do have my sio flags set to 0x80 on the target and the target has option
    KDB, DDB, and GDB in it. The target drops into the kernel debugger on a
    Ctrl-Alt-Esc and steps into the gdb backend with ">gdb", ">s" commands.

    Is there a serial port baud rate setting I need to revise? Also, I properly
    turned off the getty in /etc/ttys on the target for the sio used as the
    debugger console.

    Also, how do I get rid of the libthread_db.so undefined symbol reference to
    ps_pglobal_lookup?

    Both host and target are 5.4 although the host is a 5.2.1 updated to 5.4RC3
    updated to 5.4 RELEASE configuration...

    Lonnie VanZandt

    _______________________________________________
    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: Hanspeter Roth: "Unabel to resurrect your old /etc/x"

    Relevant Pages

    • Missing a step in new(er) Remote gdb/kdb setup?
      ... Marcel Moolenaar - or anyone who has properly setup the new remote ... FreeBSD in the 5.2.1 release prior to the gdb -k to kgdb switchover. ... I do have my sio flags set to 0x80 on the target and the target has option ...
      (freebsd-current)
    • Re: kgdb debugging
      ... Could people shed some light how to get remote debugging going, ... Two FreeBSD7 systems, target and development, connected with null ... "The remote GDB backend could not be ... In FreeBSD you can build a kernel with support for both ddb and gdb. ...
      (freebsd-questions)
    • Re: kgdb debugging
      ... Could people shed some light how to get remote debugging going, ... Two FreeBSD7 systems, target and development, connected with null ... "The remote GDB backend could not be selected" ... In FreeBSD you can build a kernel with support for both ddb and gdb. ...
      (freebsd-questions)
    • Re: kgdb debugging
      ... Could people shed some light how to get remote debugging going, ... Two FreeBSD7 systems, target and development, connected with null ... "The remote GDB backend could not be selected" ... In FreeBSD you can build a kernel with support for both ddb and gdb. ...
      (freebsd-hackers)
    • Re: Blank screen after logging into RWW
      ... You cannot connect to a remote computer or start a remote application when ... From a good working workstation in the network you should be able to ... If I go to RWW from the LAN, ... computer and/or the computer attempting to gain access to the target ...
      (microsoft.public.windows.server.sbs)
    • Quantcast