remote gdb (and firewire/dcons) not functioning as expected

From: Bruce M Simpson (bms_at_spc.org)
Date: 02/16/04

  • Next message: sebastian ssmoller: "Re: problem with ndis" 
    Date: Mon, 16 Feb 2004 19:51:01 +0000
To: freebsd-current@freebsd.org

    Hi,

    I'm trying to debug the problem introduced by the earlier commit to
    remove mbufs from the stag (MT_TAG) over the weekend.

    First of all, I tried to use dconschat to open a connection to the GDB
    port over firewire. This didn't work. dconschat complained it couldn't
    find the CROM entry on the system under test. Manual inspection of the
    CROM entries via fwcontrol(8) revealed that it was indeed present, and
    the EUI64 was typed correctly.

    Now, when I try to use 9600 baud serial (over COM1 on both machines) as
    a fallback, I get the following results (after earlier being able to
    set a breakpoint in ip_output() before the box went multiuser):-

    (kgdb) target remote /dev/cuaa0
    Remote debugging using /dev/cuaa0
    0xc0522d81 in ip_output (m=0xc10ecf, opt=0x0, ro=0x0, flags=0, imo=0x68000000,
        inp=0x38c28d01) at ../../../netinet/ip_output.c:139
    139 int hlen = sizeof (struct ip);
    warning: Unable to find dynamic linker breakpoint function.
    GDB will be unable to debug shared library initializers
    and track explicitly loaded dynamic code.
    warning: shared library handler failed to enable breakpoint
    (kgdb) step
    Can't send signals to this remote system. SIGSEGV not sent.

    Program received signal SIGSEGV, Segmentation fault.
    0xc0522d81 in ip_output (m=0xc10ecf, opt=0x0, ro=0x0, flags=0, imo=0x68000000,
        inp=0x38c28d01) at ../../../netinet/ip_output.c:139
    139 int hlen = sizeof (struct ip);
    (kgdb)

    The target system and my laptop (where I run gdb) are both seeing the
    same kernel image, which I NFS-mount from my build server.

    All boxes are running fresh -CURRENT from Saturday.

    Any ideas? This is most perplexing...

    BMS
    _______________________________________________
    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: sebastian ssmoller: "Re: problem with ndis"

    Relevant Pages

    • remote debugging help
      ... I'm trying to remotely debug an application using Visual Studio 2005. ... I attach to the remote process with a debug breakpoint set, ... I've shared out the "Remote Debugger" directory on the development machine ...
      (microsoft.public.vc.debugger)
    • Re: [RFC] hwbkpt: Hardware breakpoints (was Kwatch)
      ... Debug exceptions don't occur very often, and when they do it won't ... The global kernel allocations will already be set in the processor from the ... CPU 1 goes in and alters the user breakpoint data, ... * Hardware breakpoints are implemented using the CPU's debug registers, ...
      (Linux-Kernel)
    • Return argument has an invalid type - does remoting work reliably at all?
      ... > remote object, ... > remote object returns (I can debug to that point. ... "Advanced .Net Remoting" by Ingo Rammer, his website, msdn, articles on ... .Net Remoting is really a pain to work with. ...
      (microsoft.public.dotnet.framework.remoting)
    • RE: Assembly reported as built without debug info - that is not true
      ... enabled or without debug information:..." ... successfully remote debug any other assembly which is not in the GAC? ... in the Modules window's loading assemblies' list, ... Microsoft Online Community Support ...
      (microsoft.public.dotnet.framework)
    • RE: Debugging problems in VS2005 that didnt exist in VS2003
      ... So now I'm getting my Debug Output, albeit in the Immediate Window - at some ... > as LibB, and add this new UserControl on the AppA form. ... > the entire solution and run AppA in debug mode in VS2005, my breakpoint in ... > breakpoints in FCL code will not available now. ...
      (microsoft.public.vsnet.debugging)