From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [commit/windows] Add thread ID in SuspendThread error warning message.
Date: Wed, 19 Jun 2013 01:57:00 -0000 [thread overview]
Message-ID: <20130618234349.GH5560@adacore.com> (raw)
In-Reply-To: <20130618180156.GA7035@ednor.casa.cgf.cx>
> FWIW, I've seen this from time to time and have convinced myself that
> it's a red herring. When it happens, it probably should just silently
> continue.
That's interesting. I have the following patch in AdaCore's tree
which I have been uhming and ahming about. Would it apply to your
situation as well?
- warning (_("SuspendThread failed. (winerr %u)"),
- (unsigned) err);
- return NULL;
+ /* If SuspendThread failed with error 5 (access
+ denied), then ignore the error. It's unclear
+ where this comes from and how to prevent it.
+ But in the meantime, ignoring it seems to allow
+ us to inspect the thread (including fetching
+ registers) without apparent ill effect. */
+ if (err != 5)
+ {
+ warning (_("SuspendThread (tid=0x%x) failed."
+ " (winerr %d)"),
+ (unsigned) id, (unsigned) err);
+ return NULL;
+ }
I think there are other situations as well were we emit a warning,
and where I've been considering the idea of downgrading them to
complaints, so that users don't unnecessarily get concerned. But
I wanted to investigate a little bit before doing so, and I've
never had the time :-(.
--
Joel
next prev parent reply other threads:[~2013-06-18 23:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 10:22 Joel Brobecker
2013-06-11 10:50 ` Pedro Alves
2013-06-11 11:07 ` Joel Brobecker
2013-06-11 13:25 ` Pedro Alves
2013-06-11 16:27 ` Eli Zaretskii
2013-06-11 16:38 ` Joel Brobecker
2013-06-11 17:40 ` Eli Zaretskii
2013-06-18 18:09 ` Christopher Faylor
2013-06-19 1:57 ` Joel Brobecker [this message]
2013-06-20 18:51 ` Christopher Faylor
2013-06-24 23:45 ` Joel Brobecker
2013-06-25 21:13 ` Christopher Faylor
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=20130618234349.GH5560@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--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