This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: debugging link_map corruption
- From: Maule Mark <mark_maule at yahoo dot com>
- To: Philippe Waroquiers <philippe dot waroquiers at skynet dot be>
- Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Wed, 4 Jun 2014 13:46:00 -0700 (PDT)
- Subject: Re: debugging link_map corruption
- Authentication-results: sourceware.org; auth=none
- References: <1401888987 dot 45670 dot YahooMailNeo at web165002 dot mail dot bf1 dot yahoo dot com> <1401913266 dot 2222 dot 7 dot camel at soleil>
- Reply-to: Maule Mark <mark_maule at yahoo dot com>
Unfortunately, no. We run in a very limited diskless software environment, so there is not much opportunity for external profiling. I'm not confident that our sw stack would run under valgrind.
> On Wednesday, June 4, 2014 3:21 PM, Philippe Waroquiers <philippe.waroquiers@skynet.be> wrote:
> > On Wed, 2014-06-04 at 06:36 -0700, Maule Mark wrote:
>
>> Tried this on libc-help, no response, so trying gdb ...
>>
>> I have a heavily threaded program linked against many (~50) shared
> libraries which occasionally experiences memory corruption
>> such that the link_map list gets trashed rendering the core mostly
> undebuggable. I'm looking for ways to debug these sorts
>> of problems. My operating environment is Linux.
> Already tried Valgrind ?
>
> Philippe
>