[PATCH v2 00/36] Guile extension language for GDB

[PATCH v2 00/36] Guile extension language for GDB

[Doug Evans]

Hi.

This patch series is v2 of my first pass at adding support for the
Guile extension language.  A lot is working, but there's
still a ways to go.

guile-user: I'm going to avoid spamming you with the entire series of
36 emails.  But I may add you back to the discussion of a particular patch.

This patch series requires v4 of the "extension language API"
patch series:
https://sourceware.org/ml/gdb-patches/2014-01/msg00538.html

Summary of each patch:

01/36: configure changes
02/36: doc additions
03/36: auto-load.c changes
04/36: breakpoint.c changes
05/36: cli changes
06/36: gdbtypes.c additions
07/36: extension.c additions
08/36: guile/README
09/36: gdb-guile.exp
10/36: guile.c, guile.h
11/36: scm-auto-load.c
12/36: scm-gsmob.c
13/36: scm-exception.c, scm-safe-call.c
14/36: scm-ports.c
15/36: scm-string.c
16/36: scm-utils.c
17/36: scm-iterator.c
18/36: scm-arch.c
19/36: scm-block.c
20/36: scm-breakpoint.c
21/36: scm-disasm.c
22/36: scm-frame.c
23/36: scm-lazy-string.c
24/36: scm-math.c
25/36: scm-objfile.c
26/36: scm-pretty-print.c
27/36: scm-symbol.c
28/36: scm-symtab.c
29/36: scm-type.c
30/36: scm-value.c
31/36: Scheme files
32/36: help.exp update
33/36: generics tests
34/36: equal? tests
35/36: error tests
36/36: section script tests

Re: [PATCH v2 00/36] Guile extension language for GDB

[Doug Evans]

On Mon, Jan 20, 2014 at 1:50 PM, Doug Evans <xdje42@gmail.com> wrote:
> Hi.
>
> This patch series is v2 of my first pass at adding support for the
> Guile extension language.  A lot is working, but there's
> still a ways to go.
>
> guile-user: I'm going to avoid spamming you with the entire series of
> 36 emails.  But I may add you back to the discussion of a particular patch.
>
> This patch series requires v4 of the "extension language API"
> patch series:
> https://sourceware.org/ml/gdb-patches/2014-01/msg00538.html
>
> Summary of each patch:
>
> 01/36: configure changes
> 02/36: doc additions
> 03/36: auto-load.c changes
> 04/36: breakpoint.c changes
> 05/36: cli changes
> 06/36: gdbtypes.c additions
> 07/36: extension.c additions
> 08/36: guile/README
> 09/36: gdb-guile.exp
> 10/36: guile.c, guile.h
> 11/36: scm-auto-load.c
> 12/36: scm-gsmob.c
> 13/36: scm-exception.c, scm-safe-call.c
> 14/36: scm-ports.c
> 15/36: scm-string.c
> 16/36: scm-utils.c
> 17/36: scm-iterator.c
> 18/36: scm-arch.c
> 19/36: scm-block.c
> 20/36: scm-breakpoint.c
> 21/36: scm-disasm.c
> 22/36: scm-frame.c
> 23/36: scm-lazy-string.c
> 24/36: scm-math.c
> 25/36: scm-objfile.c
> 26/36: scm-pretty-print.c
> 27/36: scm-symbol.c
> 28/36: scm-symtab.c
> 29/36: scm-type.c
> 30/36: scm-value.c
> 31/36: Scheme files
> 32/36: help.exp update
> 33/36: generics tests
> 34/36: equal? tests
> 35/36: error tests
> 36/36: section script tests

Hi.
I have committed (most of) this series.
There's a couple of patches that can be treated as being separate, so
I'm going to commit them separately.
I'll post followups that contain the patches I actually committed
where they're different from v2.
[to minimize the amount of email]

Re: [PATCH v2 00/36] Guile extension language for GDB

[Tillmann Karras]

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).

Cheers,
Tillmann

Re: [PATCH v2 00/36] Guile extension language for GDB

[Doug Evans]

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.

Re: [PATCH v2 00/36] Guile extension language for GDB

[Tillmann Karras]

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?)

Re: [PATCH v2 00/36] Guile extension language for GDB

[Eli Zaretskii]

> 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?

Re: [PATCH v2 00/36] Guile extension language for GDB

[Doug Evans]

[+ ludovic]

On Sun, May 4, 2014 at 11:03 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> 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?

A google search for libgc 7.4 GC_MARKERS found this:

https://lists.gnu.org/archive/html/guile-commits/2014-04/msg00051.html