[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Libunwind-devel] [PATCH 5/5] Search MiniDebugInfo for procedure nam
From: |
Arun Sharma |
Subject: |
Re: [Libunwind-devel] [PATCH 5/5] Search MiniDebugInfo for procedure names |
Date: |
Sat, 18 Aug 2012 12:48:13 -0700 |
On Mon, Aug 13, 2012 at 6:58 AM, Martin Milata <address@hidden> wrote:
>> If the second lookup fails with -UNW_ENOMEM, looks like you propagate
>> that error up the stack. Why not propagate the best known answer from
>> the first lookup?
>
> The idea is that usually only the closest symbol is useful as it
> corresponds to the procedure name. If the closest symbol is too large
> and some other one that fits in the buffer is returned, it will most
> likely be name of some unrelated procedure.
>
> Also, such behaviour is consistent with what the original
> unw_get_proc_name does - it returns the closest symbol regardless of
> whether it's truncated or not. Or am I missing something?
No - this sounds fine. Was trying to make sure that this was intentional :)
I've merged this patch set as well.
-Arun
[Libunwind-devel] [PATCH 3/5] MiniDebugInfo test: tests/run-coredump-unwind-mdi, Martin Milata, 2012/08/10
[Libunwind-devel] [PATCH 4/5] Refactor parts of elfxx.c to allow reusing code, Martin Milata, 2012/08/10