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: [rfc/rfa] Use ARM exception tables as GDB unwinder


On Thu, Oct 21, 2010 at 10:29:32PM +0200, Ulrich Weigand wrote:
> Right, for C code there should be no problem.  The problems I've been
> seeing all come from *assembler* source files using the DO_CALL macro.
> This gets CFI correct, but doesn't create any unwind records ...

Oh.... yes, we could move that out of line for ARM too.  I don't like
the solution much though, because it lengthens all syscall backtraces
unnecessarily.

We're getting into the point where backtraces using the ARM unwinder
are not useful for GDB because they're flow-insensitive.  But if all
the callers of DO_CALL don't contain any other calls, we have the
option to record the ip = r7 save as if the syscall is the only
possible 'call site'.

-- 
Daniel Jacobowitz
CodeSourcery


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