From: Dan Kegel <dank@kegel.com>
To: Nikhil Bhargava <nikhilbhargav_nsit@coolgoose.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: testing mechanism for protocol stack
Date: Wed, 10 Dec 2003 09:16:12 -0800 [thread overview]
Message-ID: <3FD754DC.4010607@kegel.com> (raw)
In-Reply-To: <1071065435.2238948984@as03.coolgoose.com>
Nikhil Bhargava wrote:
> 1. Tools which help in tracking memeory leakes, stack flow and
> efficiency testing on host itself
If you can run the code on x86 in userspace, nothing beats valgrind.
- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-12-10 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 14:10 testing mechanism for protocol stack Nikhil Bhargava
2003-12-10 17:16 ` Dan Kegel [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=3FD754DC.4010607@kegel.com \
--to=dank@kegel.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=nikhilbhargav_nsit@coolgoose.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.