Hi Valgrinders
I am debugging a beast of C/C++ - ~800.000 lines of code.
I see with GCC 4.5.2 and valgrind 3.7.0 on Red Hat 5.7 64 bit, that
valgrind exits with no warning. Bummer!
With the same code and GCC 4.2.2 (32 bit) + valgrind 3.7 and valgrind
works fine, but gives several lines
On Tue, 3 Apr 2012 17:19:15 +0200, Julian Seward wrote:
On Tuesday, April 03, 2012, Peter Toft wrote:
Hi Valgrinders
I am debugging a beast of C/C++ - ~800.000 lines of code.
800k LOC is small (very) compared to some ..
Good to hear!
I see with GCC 4.5.2 and valgrind 3.7.0 on Red
On Tue, 2012-04-03 at 18:48 +0200, Peter Toft wrote:
I do not have any $LD_PRELOAD set. Should I?
Not AFAIK.
J
What is the Valgrind error-message then telling me?
This looks like bug
https://bugs.kde.org/show_bug.cgi?id=286270
which is solved in 3.8.0 SVN.
If this is the same bug,
How do I use custom memory allocators with valgrind? We'd like to use
the memory allocators from ATT libast but also like to use valgrind
for (automated) error checking. Is there any howto document how to do
this?
Olga
--
, _ _ ,
{ \/`o;-
On Tue, 2012-04-03 at 22:06 +0200, ольга крыжановская wrote:
How do I use custom memory allocators with valgrind? We'd like to use
the memory allocators from ATT libast but also like to use valgrind
for (automated) error checking. Is there any howto document how to do
this?
Olga
Philippe, libast provides both malloc replacement and a complex
allocation system based on io streams, e.g.sort of stdio with
disciplines on steroids where even string buffers, or lists and trees
of (nested) string buffers, can be a io stream or memory buffer.
Is it really wise to modify
On Tue, 2012-04-03 at 22:40 +0200, ольга крыжановская wrote:
Philippe, libast provides both malloc replacement and a complex
allocation system based on io streams, e.g.sort of stdio with
disciplines on steroids where even string buffers, or lists and trees
of (nested) string buffers, can be a
