From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Maule Mark <mark_maule@yahoo.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: debugging link_map corruption
Date: Wed, 04 Jun 2014 21:00:00 -0000 [thread overview]
Message-ID: <1401915614.2222.10.camel@soleil> (raw)
In-Reply-To: <1401914760.75029.YahooMailNeo@web165003.mail.bf1.yahoo.com>
On Wed, 2014-06-04 at 13:46 -0700, Maule Mark wrote:
> 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.
Valgrind has been used on quite "small" environments (e.g. on Android
ARM based phones), so maybe it is not *that* desperate.
If your sw stack does not run under valgrind, then that is a Valgrind
bug, which I am sure valgrind developers will be more than happy to
fix :).
Philippe
prev parent reply other threads:[~2014-06-04 21:00 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
2014-06-04 21:00 ` Philippe Waroquiers [this message]
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=1401915614.2222.10.camel@soleil \
--to=philippe.waroquiers@skynet.be \
--cc=gdb@sourceware.org \
--cc=mark_maule@yahoo.com \
/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