#2525 last cwd objPtr not released

obsolete: 8.4.4
closed
8
2003-12-17
2003-11-10
No

Get valgrind (it's free) and do the above, like so:

[on linux]
configure --disable-shared --enable-symbols
make CFLAGS_WARNING=-DPURIFY ; # add -DPURIFY
valgrind ./tclsh ; # may neeed TCL_LIBRARY set
cd ..
exit

You should find that the TclFSNormalizeAbsolutePath
(IIRC) is listed as a leaker (you may find many, but
that's one). It always happens when the function that
calls it next goes into FsUpdateCwd.

Discussion

  • Zoran Vasiljevic

    Logged In: YES
    user_id=95086

    Well, I do have Purify and when I compile tclsh
    w/o thread support and run Purify against it,
    it barks at the cwdPathPtr. If I, however, compile
    with TCL_MEM_DEBUG it barks no more and
    all is clean on app exit ( = no mem leaks).
    What I suppose is that mem debuggers get
    somehow confused with some constructs and
    produce invalid reports. I have stepped thru
    the related code with the debugger and was
    not able to see any problems in hanling the
    cwdPathPtr so far.

     
  • Zoran Vasiljevic

    Logged In: YES
    user_id=95086

    GOTCHA! There was a leak!
    I have fixed it in the cvs head and in the 8.4 branch.

     
  • Zoran Vasiljevic

    • status: open --> closed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks