From: Doug Evans <xdje42@gmail.com>
To: Tillmann Karras <tillmann@selfnet.de>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2 00/36] Guile extension language for GDB
Date: Sun, 27 Apr 2014 22:15:00 -0000 [thread overview]
Message-ID: <CAP9bCMTjnYu_d2H0SbpHp+TqvEBYxsyXZXi2Zj6iJLwTzrO58A@mail.gmail.com> (raw)
In-Reply-To: <a3c401a4a9dd02c97721c4ef99a7e652@wh-stuttgart.net>
On Sun, Apr 20, 2014 at 9:58 AM, Tillmann Karras <tillmann@selfnet.de> wrote:
> Hi.
>
> This commit series (ed3ef33944c39d9a3cea72b9a7cef3c20f0e3461) breaks "gdb
> -ex r gdb" for me. The child gdb seems to hang without getting to the
> prompt. It works when compiling current master
> (8b5c7890e8bfa3360339c303599fe5b0c9faa848) with --with-guile=no.
>
> I'm on Arch Linux testing x86_64 using the gdb-git AUR package with
> options=(!libtool debug !strip).
Hi.
I went to the trouble of installing arch-linux in a vmplayer vm, and
trying to repro this.
I can't.
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?
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.
next prev parent reply other threads:[~2014-04-27 22:15 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 [this message]
2014-05-04 19:59 ` Tillmann Karras
2014-05-05 6:03 ` Eli Zaretskii
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=CAP9bCMTjnYu_d2H0SbpHp+TqvEBYxsyXZXi2Zj6iJLwTzrO58A@mail.gmail.com \
--to=xdje42@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tillmann@selfnet.de \
/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