public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Guillaume Lewalle <guillaume.lewalle@spidcom.com>
Cc: "ecos-discuss@ecos.sourceware.org" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] ecos & valgrind
Date: Thu, 30 Aug 2007 12:13:00 -0000	[thread overview]
Message-ID: <20070830121323.GN31057@lunn.ch> (raw)
In-Reply-To: <200708301359.17958.guillaume.lewalle@spidcom.com>

On Thu, Aug 30, 2007 at 01:59:17PM +0200, Guillaume Lewalle wrote:
> hello,
> 
> is it possible to use valgrind (or some other tool) with ecos ?
> 
> if yes, anything special to do ? because all test i did with it doesn't 
> work... :-(

I assume you are using the synthetic target in Linux.

I think the answer is no, it is not possible. valgrind, at least when
checking for memory leaks, will replace the glibc malloc with its
malloc. However eCos does not use the glibc malloc. It uses the eCos
malloc. valgrind has no way to replace this, since we don't even link
with glibc. Also valgrind will rely on runtime linking, ie using .so
libraries. malloc is only linked into the image at run time and it is
then that it intercepts and puts its own malloc in place. eCos is
statically linked, so there is no chance for valgrind to get its
malloc used. 


     Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2007-08-30 12:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 11:59 Guillaume Lewalle
2007-08-30 12:13 ` Andrew Lunn [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=20070830121323.GN31057@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=guillaume.lewalle@spidcom.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).