[Bug gdb/11967] ../../src/gdb/thread.c:583: internal-error: set_running: Assertion `tp->state_ != THREAD_EXITED' failed.

[Bug gdb/11967] ../../src/gdb/thread.c:583: internal-error: set_running: Assertion `tp->state_ != THREAD_EXITED' failed.

[simark at simark dot ca]

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.

[Bug gdb/11967] ../../src/gdb/thread.c:583: internal-error: set_running: Assertion `tp->state_ != THREAD_EXITED' failed.

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=11967

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
> Do you want to try your original reproducer again, or can this be closed?

I think it's fine to close.
Thanks for trying it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/11967] ../../src/gdb/thread.c:583: internal-error: set_running: Assertion `tp->state_ != THREAD_EXITED' failed.

[tromey at redhat dot com]

------- Additional Comments From tromey at redhat dot com  2010-09-02 19:13 -------
One problem is that follow_exec calls exit_inferior_num_silent in this
situation.  That kills the thread that is about to be resumed.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11967

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.