From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: tschwinge@gnu.org (Thomas Schwinge)
Cc: pedro@codesourcery.com (Pedro Alves),
gdb@sourceware.org, ams@gnu.org (Alfred M. Szmidt),
bug-hurd@gnu.org
Subject: Re: [PATCH?] GDB HEAD (partly) broken for GNU/Hurd
Date: Mon, 13 Oct 2008 16:41:00 -0000 [thread overview]
Message-ID: <200810131640.m9DGePBo027792@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20081011174040.GI21737@fencepost.gnu.org> from "Thomas Schwinge" at Oct 11, 2008 07:40:40 PM
Thomas Schwinge wrote:
> Ha, I, myself, am the GDB guru here ;-)! I had a look at the log again,
> experimented some more, and finally got it going with the following
> patch. However, I have absolutely no idea whether that is correct in all
> cases, etc. Should perhaps target_wait (a.k.a. gnu-nat.c's gnu_wait) be
> doing that?
Adding switch_to_thread at this location seems correct to me (even though
it should be a no-op on most targets).
Could you test your patch on a non-Hurd target to make sure, anyway?
> + /* TODO. How to keep this synchronized with gnu-nat.c's own counting? */
Hmm. It would appear that "set exec-wrapper" is currently broken with
the gnu-nat.c target, right?
Thanks,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2008-10-13 16:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 9:37 Thomas Schwinge
2008-10-09 11:47 ` Alfred M. Szmidt
2008-10-09 12:46 ` Commit access for me? (was: GDB HEAD (partly) broken for GNU/Hurd) Thomas Schwinge
2008-10-09 13:21 ` Joel Brobecker
2008-10-09 11:55 ` GDB HEAD (partly) broken for GNU/Hurd Pedro Alves
2008-10-11 2:49 ` Thomas Schwinge
2008-10-11 2:50 ` Pedro Alves
2008-10-11 17:29 ` Thomas Schwinge
2008-10-11 17:43 ` [PATCH?] " Thomas Schwinge
2008-10-13 16:41 ` Ulrich Weigand [this message]
2008-10-13 18:35 ` Pedro Alves
2008-10-14 15:49 ` Thomas Schwinge
2008-10-11 17:47 ` Pedro Alves
2008-10-11 17:49 ` Thomas Schwinge
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=200810131640.m9DGePBo027792@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=ams@gnu.org \
--cc=bug-hurd@gnu.org \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tschwinge@gnu.org \
/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