From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-43380-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 20492 invoked by alias); 4 Jun 2014 21:00:17 -0000
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
Received: (qmail 20436 invoked by uid 89); 4 Jun 2014 21:00:17 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.3 required=5.0 tests=AWL,BAYES_20,KAM_FROM_URIBL_PCCC,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2
X-HELO: mailrelay008.isp.belgacom.be
Received: from mailrelay008.isp.belgacom.be (HELO mailrelay008.isp.belgacom.be) (195.238.6.174) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 04 Jun 2014 21:00:15 +0000
X-Belgacom-Dynamic: yes
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMBAN6Hj1NR88Iy/2dsb2JhbAANTIcdwAgBgSeDGQEBAQQjVhALGAICJgICVwaIWqtCd6VqF4EqjFBYB4J1gUsBA6Uzi1OBaw
Received: from 50.194-243-81.adsl-dyn.isp.belgacom.be (HELO [192.168.1.11]) ([81.243.194.50])  by relay.skynet.be with ESMTP; 04 Jun 2014 23:00:12 +0200
Subject: Re: debugging link_map corruption
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Maule Mark <mark_maule@yahoo.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
In-Reply-To: <1401914760.75029.YahooMailNeo@web165003.mail.bf1.yahoo.com>
References: <1401888987.45670.YahooMailNeo@web165002.mail.bf1.yahoo.com>	 <1401913266.2222.7.camel@soleil>	 <1401914760.75029.YahooMailNeo@web165003.mail.bf1.yahoo.com>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 04 Jun 2014 21:00:00 -0000
Message-ID: <1401915614.2222.10.camel@soleil>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
X-SW-Source: 2014-06/txt/msg00015.txt.bz2

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