This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: threads/1872: After segfault on client app "info threads"causes gdb to segfault
- From: Edward Catmur <ed at catmur dot co dot uk>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 6 Aug 2006 15:08:01 -0000
- Subject: Re: threads/1872: After segfault on client app "info threads"causes gdb to segfault
- Reply-to: Edward Catmur <ed at catmur dot co dot uk>
The following reply was made to PR threads/1872; it has been noted by GNATS.
From: Edward Catmur <ed@catmur.co.uk>
To: gdb-gnats@sources.redhat.com
Cc:
Subject: Re: threads/1872: After segfault on client app "info threads"
causes gdb to segfault
Date: Sun, 06 Aug 2006 16:05:54 +0100
Reproduced here while debugging rhythmbox. (C program with Python
scripting).
How do I get myself cc'ed on this bug?