Re: [FYI/pushed v4 08/25] Thread options & clone events (Linux GDBserver)

[Luis Machado <luis.machado@arm.com>]

On 2/6/24 14:57, Tom Tromey wrote:
>>>>>> "Luis" == Luis Machado <luis.machado@arm.com> writes:
> 
> Luis> Tromey had pointed out, on IRC, gdbserver was crashing when
> Luis> stepping over a fork on aarch64. I went to investigate it and
> Luis> noticed the testsuite run for --target_board=native-gdbserver was
> Luis> really bad in terms of FAIL's (over 700). This is Ubuntu 20.04.
> 
> I didn't try this, but I do have a fix for the fork bug.
> I'll send it in a few days, I hope.
> 
> Tom

I was checking this today. Turns out we're trying to locate the process PID of the
process in this function, line 405:

402     struct aarch64_debug_reg_state *
403     aarch64_get_debug_reg_state (pid_t pid)
404     {
405       struct process_info *proc = find_process_pid (pid);
406
407       return &proc->priv->arch_private->debug_reg_state;
408     }

But find_process_pid returns nullptr. I wonder if it is one of those cases
where we have to deal with the tid rather than the pid.

Does this look like the same case you were chasing?