From: Eli Zaretskii <eliz@gnu.org>
To: Tillmann Karras <tillmann@selfnet.de>
Cc: xdje42@gmail.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 00/36] Guile extension language for GDB
Date: Mon, 05 May 2014 06:03:00 -0000 [thread overview]
Message-ID: <83ha54zrry.fsf@gnu.org> (raw)
In-Reply-To: <f30b0b3709471cf98cf4c7a2454e9043@wh-stuttgart.net>
> Date: Sun, 04 May 2014 21:59:08 +0200
> From: Tillmann Karras <tillmann@selfnet.de>
> Cc: gdb-patches@sourceware.org
>
> On 2014-04-28 00:15, Doug Evans wrote:
> > If you're running gdb under gdb, and the child gdb is hanging,
> > can you type Ctrl-C when it hangs, and then obtain a backtrace of the
> > child gdb?
>
> Pressing Ctrl-C just prints "[New Thread 0x7ffff4b6f700 (LWP 14601)]"
> but I don't get any prompt.
My crystal ball says that Ctrl-C causes Guile to start its signal
delivery thread, which is the reason for the "New Thread" message you
see.
> > It's been suggested to give the following a try.
> > Does that fix things for you?
> >
> > bash$ export GC_MARKERS=1
> >
> > before starting gdb
> > It's a workaround for a libgc 7.4.0 bug.
> > I verified my arch-linux has libgc 7.4.0, but I may have just gotten
> > lucky.
>
> Yes, "gdb -ex 'set environment GC_MARKERS 1' -ex r gdb" makes it work
> for me. (Maybe your test VM had only one core?)
What bug is that in libgc, and what are its symptoms?
next prev parent reply other threads:[~2014-05-05 6:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 16:58 Tillmann Karras
2014-04-27 22:15 ` Doug Evans
2014-05-04 19:59 ` Tillmann Karras
2014-05-05 6:03 ` Eli Zaretskii [this message]
2014-05-12 3:25 ` Doug Evans
2014-05-12 8:00 ` GDB-Guile vs. libgc 7.4 marker threads Ludovic Courtès
2014-05-12 13:39 ` Eli Zaretskii
2014-05-13 15:53 ` Ludovic Courtès
2014-05-15 7:46 ` Andy Wingo
-- strict thread matches above, loose matches on Subject: below --
2014-01-20 21:50 [PATCH v2 00/36] Guile extension language for GDB Doug Evans
2014-02-10 5:32 ` Doug Evans
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=83ha54zrry.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tillmann@selfnet.de \
--cc=xdje42@gmail.com \
/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