From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: <gdb-patches@sourceware.org>
Subject: RE: [RFA] gdb/win32-nat.c Step the correct thread
Date: Sun, 02 Dec 2007 21:53:00 -0000 [thread overview]
Message-ID: <008f01c8352d$c312d190$493874b0$@u-strasbg.fr> (raw)
In-Reply-To: <20071202024620.GC15745@ednor.casa.cgf.cx>
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of Christopher Faylor
> Sent: Sunday, December 02, 2007 3:46 AM
> To: gdb-patches@sourceware.org; Pierre Muller
> Subject: Re: [RFA] gdb/win32-nat.c Step the correct thread
>
> On Thu, Nov 29, 2007 at 04:45:17PM +0100, Pierre Muller wrote:
> > While trying to understand the SuspendThread
> >counting problems, I tried to single step after changing
> >thread, and I noticed that the next event always
> >brought me back to the main thread.
> >
> > There is a bug in the current win32-nat.c source
> >which places the trace bit always in the
> >main thread, while we should step the thread identified by
> >inferior_ptid.
> >
> > This simple patch corrects this.
> >
> >The testsuite runs with and without this patch
> >show no difference.
> >
> >OK to check in?
>
> Ok.
Thanks, applied.
I am preparing a patch that
will get the win32 port of gdb to
honor the
set schechuler-locking on
which stipulates that only the stepped thread
will be allowed to executed and all other threads
are suspended.
The only problem is that I need to reintroduce
the suspend_count field in thread_info record
for that to work.
Pierre
prev parent reply other threads:[~2007-12-02 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 15:45 Pierre Muller
2007-12-02 2:46 ` Christopher Faylor
2007-12-02 21:53 ` Pierre Muller [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='008f01c8352d$c312d190$493874b0$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=gdb-patches@sourceware.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