Hi David, I'm still having problems! Well I tried to access a part of the memory of the unwinding-process by: elf_image + (unsigned int)addr being the elf_image = ei->image but I still do not access a valid address, do you have an example of how to use it?
Thanks, Flávio On Wed, 2007-08-15 at 19:13 -0600, David Mosberger-Tang wrote: > On 8/15/07, Jose Flavio Aguilar Paulino <[EMAIL PROTECTED]> wrote: > > > Thanks a lot for the explanation about the "min_dist", I figure out that > > the problem is in gcc optimization -O2 (Im already reporting to gcc > > developers) because it lose the min_dist value and because of that it's > > not entering in the if to fill the procedure name. > > Ah, I suspected an optimization problem! > > > Do you know how could I read the memory address space in elf file? I'm > > still trying to avoid to use the address space, but I couldn't make it > > work yet! > > The ELF file gets mmap'ed into libunwind's address-space, so you can > access it directly. The info where the image is mapped is stored in > the elf_image struct (ei->image is the starting address and ei->size > its size). > > --david -- Jose Flavio Aguilar Paulino ([EMAIL PROTECTED]) Toolchain Team LTC, Linux Technology Center IBM Brazil _______________________________________________ Libunwind-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/libunwind-devel
