On 03.06.2020 15:09, Petr Sumbera via Gdb wrote:
> This works for few test cases. And I actually started gdb tests to see 
> if it makes any regression (but it might take some time to run it though).

GDB tests on Solaris doesn't seem to deterministic. So I cannot confirm 
for 100% that the patch doesn't cause any regression. Though it rather 
seems it's not. See attached diff output between runs without and with 
the patch.

Can we get the patch to upstream now?

> But in one particular case it returns following:
> 
> ..
> [LWP    33         exited1]
> [LWP    31         exited1]
> [LWP    32         exited1]
> [LWP    28         exited1]
> [LWP    30         exited1]
> [LWP    2         exited1]
> sol_thread_fetch_registers: td_ta_map_id2thr: no thread can be found to 
> satisfy query
> sol_thread_fetch_registers: td_ta_map_id2thr: no thread can be found to 
> satisfy query
> (gdb)
> 
> It might be related...

Not sure about this one. I see this when I start Firefox with -P and 
select a profile and Firefox is going to start with selected profile. 
All threads are closed. The message is for the only remaining thread #1 
(after it got TD_NOTHR from p_td_ta_map_id2thr(). Where GDB for some 
reasons thinks it's 'defunct'.

When I run it without GDB the same process will start many other threads 
and Firefox works. In GDB the above message is shown...

Thanks,

Petr