This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: help please

From: bjorn rohde jensen <bjensen at fastmail dot fm>
To: Varun Kacholia <varunk at cse dot iitb dot ac dot in>
Cc: gcc-help at gcc dot gnu dot org
Date: Sat, 12 Oct 2002 10:30:26 +0200
Subject: Re: help please
References: <20021011215445.15951.qmail@web9406.mail.yahoo.com> <3DA74A11.20702@fastmail.fm> <20021012094451.A25476@cse.iitb.ac.in>
Reply-to: bjensen at fastmail dot fm

Hi Varun,

 I am sure, i have heard of a small library to get
stack traces from within C/C++ code, but i never tried
and forgot all about it.:)
 There are tons of memory debuggers available, if you
ask google:), i use ElectricFence once in a while, and
i am pretty happy with it. I have not had much luck
with leak detectors so far.
 I must say, i prefer proper unit testing etc to debugging,
but it is not easy to avoid entirely.

Yours sincerely,

Bjorn

References:
- help please
  - From: Charles Graham
- Re: help please
  - From: bjorn rohde jensen
- Re: help please
  - From: Varun Kacholia

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]