From: Maule Mark <mark_maule@yahoo.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: debugging link_map corruption
Date: Wed, 04 Jun 2014 20:46:00 -0000 [thread overview]
Message-ID: <1401914760.75029.YahooMailNeo@web165003.mail.bf1.yahoo.com> (raw)
In-Reply-To: <1401913266.2222.7.camel@soleil>
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
>
next prev parent reply other threads:[~2014-06-04 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 13:36 Maule Mark
2014-06-04 20:21 ` Philippe Waroquiers
2014-06-04 20:46 ` Maule Mark [this message]
2014-06-04 21:00 ` Philippe Waroquiers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1401914760.75029.YahooMailNeo@web165003.mail.bf1.yahoo.com \
--to=mark_maule@yahoo.com \
--cc=gdb@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox