public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/11967] ../../src/gdb/thread.c:583: internal-error: set_running: Assertion `tp->state_ != THREAD_EXITED' failed.
Date: Fri, 16 Apr 2021 20:14:47 +0000 [thread overview]
Message-ID: <bug-11967-4717-5mNydSpfXX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11967-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=11967
--- Comment #4 from Simon Marchi <simark at simark dot ca> ---
(In reply to Simon Marchi from comment #2)
> This still exists today. I did
>
> ./gdb -nx -q --data-directory=data-directory t -ex "catch exec" -ex "set
> follow-exec-mode new" -ex "set non-stop on" -ex "run"
>
> Where t is compiled from the following program:
>
> #include <stdio.h>
> #include <string.h>
> #include <unistd.h>
>
> int
> main (void)
> {
> char *exec_args[] = { "/bin/ls", "ppp", NULL };
> execve (exec_args[0], exec_args, NULL);
> }
This toy test case passes now, I bisected and the failure disappeared with
080363310650c93ad8e93018bcb6760ba5d32d1c
Per-inferior thread list, thread ranges/iterators, down with ALL_THREADS,
etc.
Do you want to try your original reproducer again, or can this be closed?
--
You are receiving this mail because:
You are on the CC list for the bug.
next parent reply other threads:[~2021-04-16 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11967-4717@http.sourceware.org/bugzilla/>
2021-04-16 20:14 ` simark at simark dot ca [this message]
2021-04-17 16:53 ` tromey at sourceware dot org
2010-09-02 16:56 [Bug gdb/11967] New: " tromey at redhat dot com
2010-09-02 19:13 ` [Bug gdb/11967] " tromey at redhat dot com
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=bug-11967-4717-5mNydSpfXX@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).