From: Thomas Schwinge <tschwinge@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb@sourceware.org, "Alfred M. Szmidt" <ams@gnu.org>,
uweigand@de.ibm.com, bug-hurd@gnu.org
Subject: Re: GDB HEAD (partly) broken for GNU/Hurd
Date: Sat, 11 Oct 2008 17:49:00 -0000 [thread overview]
Message-ID: <20081011174617.GZ7127@fencepost.gnu.org> (raw)
In-Reply-To: <200810111846.32013.pedro@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
Hello!
On Sat, Oct 11, 2008 at 06:46:31PM +0100, Pedro Alves wrote:
> > STOPPED_BY_WATCHPOINT () = 0
> > infrun: context switch
> > infrun: Switching context from bogus thread id 1 to Thread 25830.3
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> This is missing in the new implementation. In Hurd when going through
> the shell doing fork/execs, we see new threads at every exec, and the
> old threads disappear. Could you try adding a `switch_to_thread (resume_thread)'
> somewhere after target_wait returns and before any other target method?
Haha!, see my other email. :-D
Regards,
Thomas
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
prev parent reply other threads:[~2008-10-11 17:49 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
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 [this message]
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=20081011174617.GZ7127@fencepost.gnu.org \
--to=tschwinge@gnu.org \
--cc=ams@gnu.org \
--cc=bug-hurd@gnu.org \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=uweigand@de.ibm.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