Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Taylor <dtaylor@emc.com>
To: gdb@sourceware.org
Subject: internal GDB error mourning inferior
Date: Fri, 24 May 2013 20:15:00 -0000	[thread overview]
Message-ID: <29865.1369426532@usendtaylorx2l> (raw)

In an unmodified gdb 7.6 , unmodified gdb 7.4.1, and a gdb 7.2-ubuntu,
the following sequence of steps will lead to an internal error:

. start up a gdb server listening on local port 5432.

. freshly started gdb, no exec file, type:

    target remote 127.0.0.1:5432

. kill / exit the gdb server

. back at gdb do:

    target remote 127.0.0.1:5432

again.

In 7.2-ubuntu it says:

    /build/buildd/gdb-7.2/gdb/target.c:2330: internal-error: could not find a target to follow mourn inferior
    A problem internal to GDB has been detected,
    further debugging may prove unreliable.
    Quit this debugging session? (y or n) y

In 7.6, invoked with -i=mi (this is where the problem was origianlly
noticed), the complete output is:


    =thread-group-added,id="i1"
    ~"GNU gdb (GDB) 7.6\n"
    ~"Copyright (C) 2013 Free Software Foundation, Inc.\n"
    ~"License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law.  Type \"show copying\"\nand \"show warranty\" for details.\n"
    ~"This GDB was configured as \"--host=i686-pc-linux-gnu --target=x86_64-unknown-linux-gnu\".\nFor bug reporting instructions, please see:\n"
    ~"<http://www.gnu.org/software/gdb/bugs/>.\n"
    (gdb) 
    target remote localhost:5432
    &"target remote localhost:5432\n"
    ~"Remote debugging using localhost:5432\n"
    =thread-group-started,id="i1",pid="42000"
    =thread-created,id="1",group-id="i1"
    ~"0x00000000 in ?? ()\n"
    *stopped,frame={addr="0x00000000",func="??",args=[]},thread-id="1",stopped-threads="all"
    ^done
    (gdb) 
    target remote localhost:5432
    &"target remote localhost:5432\n"
    =thread-group-exited,id="i1"
    &"Remote connection closed\n"
    Abort (core dumped)

I have not tried it with top of trunk.

If it matters, it was built to be hosted on i686-pc-linux-gnu,
targetting x86_64-unknown-linux-gnu, running on an x86-64 linux box.

[The targets we want to debug are x86-64, but not everyone has a 64 bit
desktop as yet; however, everyone has an Intel based GNU/Linux box.]


             reply	other threads:[~2013-05-24 20:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 20:15 David Taylor [this message]
2013-05-24 22:34 ` Luis Machado
2013-05-28 17:42   ` David Taylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=29865.1369426532@usendtaylorx2l \
    --to=dtaylor@emc.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox