Re: [patch] Backtrace prints wrong argument value

Luis Machado
2007-05-16T05:34:17Z

On Wed, 2007-04-25 at 15:13 -0400, Daniel Jacobowitz wrote:
> A valid location list for func1 could say that arg1 is valid
> in r20 during the call to abort; the -1 puts us on the call, instead
> of after it, in the unrelated func2.
>
> I believe this is considered a known weakness of the DWARF
> representation, which does not represent state before an instruction
> separately from state after it. The debug info does not tell us
> whether the location is valid in the middle of the call.

Do you have anything in mind in order to better handle this situation
instead of showing wrong values in backtrace every now and then?

From your comment it wasn't clear if hiding possibly wrong values is
worse than showing them sometimes.

Regards,
Luis