From: Oswald Buddenhagen <oswald.buddenhagen@trolltech.de>
To: gdb-patches@sourceware.org
Subject: Re: make attaching to stopped processes work under windows
Date: Mon, 02 Mar 2009 10:07:00 -0000 [thread overview]
Message-ID: <20090302100651.GA8157@troll08.nokia.trolltech.de> (raw)
In-Reply-To: <20090228004414.GA21767@ednor.casa.cgf.cx>
hi,
On Fri, Feb 27, 2009 at 07:44:14PM -0500, Christopher Faylor wrote:
> On Thu, Feb 26, 2009 at 08:25:52PM +0100, Oswald Buddenhagen wrote:
> >the rationale is in the patch itself; i can factor it out to the commit
> >message if preferred.
> >
> > * windows-nat.c (get_windows_debug_event): If we find the thread
> > from the CREATE_PROCESS_DEBUG_EVENT suspended, resume it.
>
> Suspending random threads like this is usually a bad idea. Do you
> actually have a use cause that requires attaching to suspended threads?
>
i should point out that the patch contains a comment answering that
question and that i pointed that out in the only sentence the mail
contained. so please be a little bit more attentive, or make it somewhat
clearer that you already are (by relating to previous content when you
ask something). thanks.
next prev parent reply other threads:[~2009-03-02 10:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 15:04 Oswald Buddenhagen
2009-02-28 7:15 ` Christopher Faylor
2009-03-02 10:07 ` Oswald Buddenhagen [this message]
2009-03-02 17:23 ` Joel Brobecker
2009-03-02 18:28 ` Oswald Buddenhagen
2009-03-02 19:18 ` Eli Zaretskii
2009-03-02 19:55 ` Oswald Buddenhagen
2009-03-02 21:21 ` Eli Zaretskii
2009-03-03 5:21 ` Christopher Faylor
2009-03-03 12:05 ` Oswald Buddenhagen
2009-03-08 19:32 ` Christopher Faylor
2009-03-09 18:45 ` Joel Brobecker
2009-03-09 20:51 ` Oswald Buddenhagen
2009-03-10 8:52 ` Christopher Faylor
2009-03-10 13:37 ` Oswald Buddenhagen
2009-03-03 5:41 ` Christopher Faylor
2009-03-02 19:14 ` Eli Zaretskii
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=20090302100651.GA8157@troll08.nokia.trolltech.de \
--to=oswald.buddenhagen@trolltech.de \
--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