|
From: Mathieu L. <mat...@gm...> - 2010-06-23 08:45:23
|
hi, I use valgrind on a normal x86 FC12 system except that it runs an adhoc dynamic loader whose specifics is to allow users to load the same file more than once at different base addresses. Things work nicely if I am careful not to load the same file more than once at any given time but valgrind appears to have trouble resolving symbols in anything but the first version of the file loaded in memory. Could it be that when valgrind loads the debuginfo associated to a specific elf file loaded in memory, it loads it in a way which makes that debuginfo entirely specific to the base address of that file ? If so, is there someone with a really bright idea about how I could work around that in valgrind so that valgrind resolves the symbols of all the versions of the file loaded in memory ? Mathieu -- Mathieu Lacage <mat...@gm...> |
|
From: Mathieu L. <mat...@gm...> - 2010-06-23 09:22:00
Attachments:
loader.patch
|
something like the attached patch eventually allowed me to force valgrind to load the needed debug information more than once when needed. Is there something I can do to help get this merged so that I don't have to ask my users to apply this patch themselves ? On Wed, Jun 23, 2010 at 10:45 AM, Mathieu Lacage <mat...@gm...> wrote: > hi, > > I use valgrind on a normal x86 FC12 system except that it runs an > adhoc dynamic loader whose specifics is to allow users to load the > same file more than once at different base addresses. Things work > nicely if I am careful not to load the same file more than once at any > given time but valgrind appears to have trouble resolving symbols in > anything but the first version of the file loaded in memory. Could it > be that when valgrind loads the debuginfo associated to a specific elf > file loaded in memory, it loads it in a way which makes that debuginfo > entirely specific to the base address of that file ? If so, is there > someone with a really bright idea about how I could work around that > in valgrind so that valgrind resolves the symbols of all the versions > of the file loaded in memory ? > > Mathieu > -- > Mathieu Lacage <mat...@gm...> > -- Mathieu Lacage <mat...@gm...> |
|
From: Mathieu L. <mat...@gm...> - 2010-06-29 11:53:38
|
ok, I attached a complete reduced testcase and patch to the following bug report. Enjoy ! https://bugs.kde.org/show_bug.cgi?id=243153 On Wed, Jun 23, 2010 at 11:21 AM, Mathieu Lacage <mat...@gm...> wrote: > something like the attached patch eventually allowed me to force > valgrind to load the needed debug information more than once when > needed. Is there something I can do to help get this merged so that I > don't have to ask my users to apply this patch themselves ? > > On Wed, Jun 23, 2010 at 10:45 AM, Mathieu Lacage > <mat...@gm...> wrote: >> hi, >> >> I use valgrind on a normal x86 FC12 system except that it runs an >> adhoc dynamic loader whose specifics is to allow users to load the >> same file more than once at different base addresses. Things work >> nicely if I am careful not to load the same file more than once at any >> given time but valgrind appears to have trouble resolving symbols in >> anything but the first version of the file loaded in memory. Could it >> be that when valgrind loads the debuginfo associated to a specific elf >> file loaded in memory, it loads it in a way which makes that debuginfo >> entirely specific to the base address of that file ? If so, is there >> someone with a really bright idea about how I could work around that >> in valgrind so that valgrind resolves the symbols of all the versions >> of the file loaded in memory ? >> >> Mathieu >> -- >> Mathieu Lacage <mat...@gm...> >> > > > > -- > Mathieu Lacage <mat...@gm...> > -- Mathieu Lacage <mat...@gm...> |
|
From: Mathieu L. <mat...@gm...> - 2010-07-17 13:46:35
|
that's a ping. On Tue, Jun 29, 2010 at 1:45 PM, Mathieu Lacage <mat...@gm...> wrote: > ok, I attached a complete reduced testcase and patch to the following > bug report. Enjoy ! > > https://bugs.kde.org/show_bug.cgi?id=243153 is there something I can do to help get this issue fixed in the next release of valgrind ? Mathieu -- Mathieu Lacage <mat...@gm...> |