This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA] dwarf2loc, guard against null


Daniel Jacobowitz (drow@false.org):

> I'm not sure - there must be another bug so it might be this should be
> a gdb_assert instead.  The DW_AT_frame_base that brought us here came
> from .debug_info inside an entry for a function.  So we must have
> found the function at some point.  But we didn't find the function
> this time - why not?

Hmmm... Let me have a closer look. In my case, the problem appears when
debugging an application on VxWorks, with this scenario:
* breakpoint hit;
* print the address of a variable in the current frame (print &DB);
* resume the execution; program exited normally;
* retry to print the variable => end up in dwarf_expr_frame_base,
no frame, crash.

We are (probably) still using a wrong .debug_info at this point.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]