Re: [Texmacs-dev] Using Valgrind and first results

[Joris van der Hoeven]

> ==4199== 5520 bytes in 3 blocks are definitely lost in loss record 94 of 105
> ==4199==    at 0x3C01F40D: malloc (vg_replace_malloc.c:105)
> ==4199==    by 0x817EED0: safe_malloc(unsigned) (fast_alloc.cpp:35)
> ==4199==    by 0x80570E7: operator new[](unsigned) (basic.cpp:62)
> ==4199==    by 0x8273F2D: as_charp(string) (string.cpp:235)
>
> Is there a leak here?
>
> ==4199==
> ==4199== ---- Print suppression ? --- [Return/N/n/Y/y/C/c] ---- n
> ==4199==
> ==4199==
> ==4199== 1007792 bytes in 287 blocks are possibly lost in loss record 103 of 
> 105
> ==4199==    at 0x3C01F40D: malloc (vg_replace_malloc.c:105)
> ==4199==    by 0x817EED0: safe_malloc(unsigned) (fast_alloc.cpp:35)
> ==4199==    by 0x80570E7: operator new[](unsigned) (basic.cpp:62)
> ==4199==    by 0x80CE2B0: hashmap_rep<tree_label, tag_info>::resize(int) 
> (hashmap.cpp:54)
>
> And here?

Would it be possible to get a backtrace which goes slightly further
than four items? Also: is it possible to teach valgrind how to
display the lost blocks?