From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Fix internal error with 'set debug infrun 1' under high load
Date: Sun, 24 Mar 2019 21:09:00 -0000 [thread overview]
Message-ID: <1553461783.1504.3.camel@skynet.be> (raw)
In-Reply-To: <20190324135043.043ef0d9@f29-4.lan>
On Sun, 2019-03-24 at 13:50 -0700, Kevin Buettner wrote:
> Hi Philippe,
>
> There is definitely a bug in this section of code from infrun.c:
>
> else if (ws.kind == TARGET_WAITKIND_THREAD_EXITED
> || ws.kind == TARGET_WAITKIND_EXITED
> || ws.kind == TARGET_WAITKIND_SIGNALLED)
> {
> if (debug_infrun)
> {
> ptid_t ptid = ptid_t (ws.value.integer);
>
> fprintf_unfiltered (gdb_stdlog,
> "infrun: %s exited while "
> "stopping threads\n",
> target_pid_to_str (ptid).c_str ());
> }
> }
>
> This line...
>
> ptid_t ptid = ptid_t (ws.value.integer);
>
> ...doesn't make sense to me since ws.value.integer is supposed to
> be the exit status for TARGET_WAITKIND_THREAD_EXITED and
> TARGET_WAITKIND_EXITED.
>
> However, for TARGET_WAITKIND_SIGNALLED, the signal number is in
> ws.value.sig (which, due to being part of a union occupies some
> of the same bytes as ws.value.integer).
>
> So trying to find the ptid in that manner makes no sense at all.
>
> I'm guessing that the ptid values are bogus when it does work.
>
> Does it work when you use
>
> ptid_t ptid = ptid_t (event_pid);
>
> instead?
I guess you mean to only print event_ptid.
Yes, that is working (the proposed patch was printing both
event_ptid and the ptid derived from ws.value.integer, assuming
that sometimes ws.value.integer was something relevant).
Here is the trace I obtain after a few trials under high load:
infrun: stop_all_threads, pass=0, iterations=0
infrun:Â Â Â Thread 0x7ffff7fcfb40 (LWP 3587) not executing
infrun:Â Â Â Thread 0x7ffff7310700 (LWP 3632) executing, need stop
[Thread 0x7ffff7310700 (LWP 3632) exited]
infrun: target_wait (-1.0.0, status) =
infrun:Â Â Â 3587.3632.0 [LWP 3632],
infrun:Â Â Â status->kind = thread exited, status = 0
infrun: LWP 3632 exited while stopping threads
infrun:Â Â Â Thread 0x7ffff7fcfb40 (LWP 3587) not executing
infrun: stop_all_threads, pass=1, iterations=1
infrun:Â Â Â Thread 0x7ffff7fcfb40 (LWP 3587) not executing
infrun: stop_all_threads done
The above is obtained with the patch:
diff --git a/gdb/infrun.c b/gdb/infrun.c
index ad7892105a..7f1339a917 100644
--- a/gdb/infrun.c
+++ b/gdb/infrun.c
@@ -4365,12 +4365,10 @@ stop_all_threads (void)
            {
              if (debug_infrun)
                {
-Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ptid_t ptid = ptid_t (ws.value.integer);
-
                  fprintf_unfiltered (gdb_stdlog,
                                      "infrun: %s exited while "
                                      "stopping threads\n",
-Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â target_pid_to_str (ptid).c_str ());
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â target_pid_to_str (event_ptid).c_str ());
                }
            }
          else
next prev parent reply other threads:[~2019-03-24 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 14:25 Philippe Waroquiers
2019-03-24 20:50 ` Kevin Buettner
2019-03-24 21:09 ` Philippe Waroquiers [this message]
2019-03-24 21:35 ` Kevin Buettner
2019-03-24 21:40 ` Philippe Waroquiers
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=1553461783.1504.3.camel@skynet.be \
--to=philippe.waroquiers@skynet.be \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.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