Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@schwinge.name>
To: svante.signell@telia.com
Cc: gdb-patches@sourceware.org
Subject: Re: Patch to enable a fully working gdb for GNU/Hurd
Date: Mon, 04 Jul 2011 18:34:00 -0000	[thread overview]
Message-ID: <87k4bxj4ed.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <1309367642.3172.82.camel@s1499.it.kth.se>

[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]

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?


Grüße,
 Thomas

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2011-07-04 18:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29 17:14 Svante Signell
2011-07-04 18:34 ` Thomas Schwinge [this message]
2011-07-04 19:20   ` Svante Signell
2011-07-04 19:56     ` Joel Brobecker
2011-07-05 14:53     ` Svante Signell
2011-07-05 15:09       ` Thomas Schwinge
2011-07-05 16:26       ` Tom Tromey
2011-07-05 17:51         ` Svante Signell

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=87k4bxj4ed.fsf@kepler.schwinge.homeip.net \
    --to=thomas@schwinge.name \
    --cc=gdb-patches@sourceware.org \
    --cc=svante.signell@telia.com \
    /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