This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2 00/36] Guile extension language for GDB
- From: Tillmann Karras <tillmann at selfnet dot de>
- To: Doug Evans <xdje42 at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sun, 04 May 2014 21:59:08 +0200
- Subject: Re: [PATCH v2 00/36] Guile extension language for GDB
- Authentication-results: sourceware.org; auth=none
- References: <a3c401a4a9dd02c97721c4ef99a7e652 at wh-stuttgart dot net> <CAP9bCMTjnYu_d2H0SbpHp+TqvEBYxsyXZXi2Zj6iJLwTzrO58A at mail dot gmail dot com>
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.
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?)