This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Patch to enable a fully working gdb for GNU/Hurd
- From: Svante Signell <svante dot signell at telia dot com>
- To: Thomas Schwinge <thomas at schwinge dot name>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 04 Jul 2011 21:17:43 +0200
- Subject: Re: Patch to enable a fully working gdb for GNU/Hurd
- References: <1309367642.3172.82.camel@s1499.it.kth.se> <87k4bxj4ed.fsf@kepler.schwinge.homeip.net>
- Reply-to: svante dot signell at telia dot com
On Mon, 2011-07-04 at 20:18 +0200, Thomas Schwinge wrote:
> Hallo!
>
> On Wed, 29 Jun 2011 19:14:02 +0200, Svante Signell <svante.signell@telia.com> wrote:
> > Here is an attempt to create a complete patch for gdb to make it run
> > successfully on GNU/Hurd.
> >
> > Problem description:
> > When starting gdb the following output is written:
> > Can't fetch registers from thread bogus thread id 1: No such thread
> >
> > This makes gdb completely unusable for debugging purposes without this
> > patch.
> >
> > Patch size: Small change
> >
> > ChangeLog:
> > gdb/
> > 2011-06-29 Svante Signell <svante.signell@telia.com>
> >
> > * gnu_nat.c: Activate prune_threads() for Hurd
> > * thread.c: Make prune_threads() visible outside current scope.
> > * gdbthread.h: Declare prune_threads()
> > * Fix PR gdb/12222
>
> At the time I had originally written this patch, I rather considered it
> to be a hack than a proper fix -- I just needed a functional GDB on
> GNU/Hurd back then.
>
> I think that update_thread_list (which already is exported) should rather
> be invoked instead of additionally exporting prune_threads.
>
> But -- I can no longer reproduce the original problem with GDB HEAD. Can
> you?
I haven't compiled gdb for some time now. I can take a look, how to get
the GDB HEAD? The prune_threads enabled gdb to work properly, and then
Samuel applied an earlier version of the patch on debian-ports.
Since then the new Debian gdb maintainer wanted to get this patch
applied upstream, so I did as was requested. Don't know if it is the
correct approach or not. I can try to use update_thread_list instead,
once I have the GDB HEAD files.