[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Libunwind-devel] [PATCH 3/7] Fix issue with resolving relative addr
|
From: |
ext Daniel Jacobowitz |
|
Subject: |
Re: [Libunwind-devel] [PATCH 3/7] Fix issue with resolving relative addresses for prelinked libraries |
|
Date: |
Wed, 25 Jun 2008 10:06:17 -0400 |
|
User-agent: |
Mutt/1.5.17 (2008-05-11) |
On Wed, Jun 25, 2008 at 08:51:31AM -0400, Anderson Lizardo wrote:
> Do you have any suggestions on how to reliably calculate absolute
> addresses? An alternative approach I have in mind is to peek directly at
> the linker structures, like it's done by GDB. Is that the only feasible
> general solution to the issue?
I'm not sure I understand what you're doing. Don't you already have
the run-time linker's offsets? If you assume that any file you've
opened is the same as the one running in the target process, then all
it takes is combining the two; p_vaddr plus the offset from the link
map.
It's much trickier in GDB because we support remote debugging and
core dumps; the library may have been re-prelinked to a different
address.
--
Daniel Jacobowitz
CodeSourcery
- Re: [Libunwind-devel] [PATCH 7/7] Implement _UPTi_find_unwind_table() for ARM, (continued)
[Libunwind-devel] [PATCH 2/7] Change debuglink lookup order, Anderson Lizardo, 2008/06/25
[Libunwind-devel] [PATCH 1/7] ARM: add missing register offsets, Anderson Lizardo, 2008/06/25
[Libunwind-devel] [PATCH 3/7] Fix issue with resolving relative addresses for prelinked libraries, Anderson Lizardo, 2008/06/25
[Libunwind-devel] [PATCH 4/7] Add path and pathlen arguments to tdep_get_elf_image(), Anderson Lizardo, 2008/06/25
Re: [Libunwind-devel] [PATCH 0/7] ARM: add remote backtrace support, Daniel Jacobowitz, 2008/06/25