texmacs-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Joris van der Hoeven
Subject: Re: [Texmacs-dev] Using Valgrind and first results
Date: Tue, 25 May 2004 16:10:36 +0200 (CEST)

On Tue, 25 May 2004, David MENTRE wrote:
> Joris van der Hoeven <address@hidden> writes:
> ==7818== 5520 bytes in 3 blocks are definitely lost in loss record 94 of 105
> ==7818==    at 0x3C01F40D: malloc (vg_replace_malloc.c:105)
> ==7818==    by 0x817EED0: safe_malloc(unsigned) (fast_alloc.cpp:35)
> ==7818==    by 0x80570E7: operator new[](unsigned) (basic.cpp:62)
> ==7818==    by 0x8273F2D: as_charp(string) (string.cpp:235)
> ==7818==    by 0x8276286: set_env(string, string) (sys_utils.cpp:80)
> ==7818==    by 0x81DD3E4: set_env_path(string, url) (init_texmacs.cpp:42)
> ==7818==    by 0x81DD509: get_env_path(string, url) (init_texmacs.cpp:49)
> ==7818==    by 0x81DE764: init_env_vars() (init_texmacs.cpp:220)
> ==7818==    by 0x81DFEC6: init_texmacs() (init_texmacs.cpp:388)
> ==7818==    by 0x830FF55: main (texmacs.cpp:208)
> ==7818==
> ==7818==
> ==7818== 2031616 bytes in 31 blocks are still reachable in loss record 103 of 
> 105
> ==7818==    at 0x3C01F40D: malloc (vg_replace_malloc.c:105)
> ==7818==    by 0x817EED0: safe_malloc(unsigned) (fast_alloc.cpp:35)
> ==7818==    by 0x817EF1C: enlarge_malloc(unsigned) (fast_alloc.cpp:46)
> ==7818==    by 0x8057004: operator new(unsigned) (basic.cpp:25)
> ==7818==    by 0x8051C6E: tree::tree(char*) (tree.hpp:141)
> ==7818==    by 0x809B0D0: url_none() (url.hpp:60)
> ==7818==    by 0x830CF36: __static_initialization_and_destruction_0(int, int) 
> (tm_server.cpp:22)
> ==7818==    by 0x830D0A5: _GLOBAL(i_xx_t, short,...)(long double, 
> void,...)(long double) (tm_server.cpp:49)
> ==7818==    by 0x8310104: (within 
> /home/david/00-poubelle/texmacs/libexec/TeXmacs/bin/texmacs.bin)
> ==7818==    by 0x804AA78: (within 
> /home/david/00-poubelle/texmacs/libexec/TeXmacs/bin/texmacs.bin)
> ==7818==
> ==7818==
> ==7818== 2048660 bytes in 202 blocks are possibly lost in loss record 104 of 
> 105
> ==7818==    at 0x3C01F40D: malloc (vg_replace_malloc.c:105)
> ==7818==    by 0x817EED0: safe_malloc(unsigned) (fast_alloc.cpp:35)
> ==7818==    by 0x80570E7: operator new[](unsigned) (basic.cpp:62)
> ==7818==    by 0x80CE2B0: hashmap_rep<tree_label, tag_info>::resize(int) 
> (hashmap.cpp:54)
> ==7818==    by 0x80CE193: hashmap_rep<tree_label, 
> tag_info>::bracket_rw(tree_label) (hashmap.cpp:89)
> ==7818==    by 0x80CDE4D: hashmap<tree_label, 
> tag_info>::operator()(tree_label) (hashmap.hpp:83)
> ==7818==    by 0x80CD7B1: rel_hashmap<tree_label, 
> tag_info>::operator()(tree_label) (rel_hashmap.cpp:35)
> ==7818==    by 0x80CF2AD: init(tree_label, string, tag_info) (drd_std.cpp:45)
> ==7818==    by 0x80D414E: init_std_drd() (drd_std.cpp:215)
> ==7818==    by 0x81DFEB2: init_texmacs() (init_texmacs.cpp:384)

Thanks; that is interesting. Could it be that global variables
which are not destroyed at exit are reported? I probably should
cleanly destroy all of them before exiting.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]