Re: ARM/linux gdb stops and gives no info

[Fernando Nasser <fnasser at cygnus dot com>]

"Peter.Schauer" wrote:
> 
> It was a safety measure to avoid GDB core dumps if selected_frame == NULL.
> If you really want to reproduce the original problem, get gdb-4.15.1, build
> it on sparc Solaris and (mostly from the original bug report):
> 
It did look like protection against a core dump.  My hope was that the reason for that
was cleared already. Unfortunately that does not seem to be the case.

>
> With CVS GDB, do_registers_info calls read_relative_register_raw_bytes
> which in turn calls read_relative_register_raw_bytes_for_frame with
> selected_frame.
> 
> So even nowadays generic do_registers_info might need a valid selected_frame,
> and your proposed patch would not help.
> 
> I'd prefer to keep the selected_frame != NULL check in registers_info
> and rather make sure that selected_frame is not NULL in Richard's case,
> although I do not know if this can be done for the ARM.
> 
This would be the right solution.

> On the other hand we could remove the check in registers_info and wait for
> bug reports with GDB crashing in registers_info due to selected_frame == NULL
> and fix their cause.
> 
I rather not having core dumps...
We can leave the test and wait for people to complain about it.  Or even make
it an internal_error (where you have the option to dump core and it is more
annoying).


> Has to be decided by the maintainer of infcmd.c (Fernando ? :-).
> 
Not me.


-- 
Fernando Nasser
Red Hat - Toronto                       E-Mail:  fnasser@cygnus.com
2323 Yonge Street, Suite #300           Tel:  416-482-2661 ext. 311
Toronto, Ontario   M4P 2C9              Fax:  416-482-6299