Re: [paragui-users] valgrind and memory leaks in paragui

[Robby Dermody]

FYI, I'm subscribed to the PhysicsFS list, Ryan fixed the PHYSFS leaks, the
changes are in CVS.
I'll mail him this letter to make sure he got all the ones listed here.

Robby

----- Original Message -----
From: "andy uehara" <address@hidden>
To: <address@hidden>
Sent: Monday, July 29, 2002 4:29 AM
Subject: [paragui-users] valgrind and memory leaks in paragui


> hello all,
> I recently tried out valgrind. Sort of a sandbox that
> you run your programs in. It basically tracks any kind
> of memory allocation, pthread locking and other
> goodness.
>
> http://developer.kde.org/~sewardj/
>
> I ran it with my program and I got a bunch of stuff:
> ...<snip>
> ==30096==
> ==30096== ERROR SUMMARY: 293 errors from 16 contexts
> (suppressed: 116 from 2)
> ==30096== malloc/free: in use at exit: 65485 bytes in
> 68 blocks.
> ==30096== malloc/free: 5498 allocs, 5430 frees,
> 4006432 bytes allocated.
> ==30096==
> ==30096== 11 bytes in 1 blocks are definitely lost in
> loss record 1 of 8
> ==30096==    at 0x4004328B: malloc
> (vg_clientfuncs.c:100)
> ==30096==    by 0x4030BA4A: copyEnvironmentVariable
> (platform.c:180)
> ==30096==    by 0x4030BD1A:
> __PHYSFS_platformGetUserDir (platform.c:288)
> ==30096==    by 0x403097B6: calculateUserDir
> (physfs.c:276)
> ==30096==
> ==30096== 56 bytes in 14 blocks are definitely lost in
> loss record 4 of 8
> ==30096==    at 0x4004328B: malloc
> (vg_clientfuncs.c:100)
> ==30096==    by 0x4030F1A6: ZIP_openRead (zip.c:647)
> ==30096==    by 0x4030B255: PHYSFS_openRead
> (physfs.c:1276)
> ==30096==    by 0x40319F15: PHYSFSRWOPS_openRead
> (physfsrwops.cpp:175)
> ==30096==
> ==30096== 2464 bytes in 22 blocks are definitely lost
> in loss record 7 of 8
> ==30096==    at 0x4004337B: __builtin_new
> (vg_clientfuncs.c:126)
> ==30096==    by 0x40332958:
> PG_Button::PG_Button(PG_Widget *, int, PG_Rect const
> &, char const *, char const *) (pgbutton.cpp:55)
> ==30096==    by 0x40342E44:
> PG_ScrollBar::PG_ScrollBar(PG_Widget *, int, PG_Rect
> const &, int, char const *) (pgscrollbar.cpp:100)
> ==30096==    by 0x4034CC90:
> PG_WidgetList::PG_WidgetList(PG_Widget *, PG_Rect
> const &, char const *) (pgwidgetlist.cpp:78)
> ==30096==
>
> ==30096== LEAK SUMMARY:
> ==30096==    definitely lost: 2531 bytes in 37 blocks.
> ==30096==    possibly lost:   0 bytes in 0 blocks.
> ==30096==    still reachable: 62954 bytes in 31
> blocks.
>
> I just tried it, and I am not sure where all the
> errors are coming from, but this is what it spits out.
> There are also lots of pthread locking warnings.
>
> Hopefully someone more knowledgable will see this and
> know how to fix some of these.
>
> andy
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Health - Feel better, live better
> http://health.yahoo.com
>
> _______________________________________________
> paragui-users mailing list
> address@hidden
> http://mail.freesoftware.fsf.org/mailman/listinfo/paragui-users
>