[Pdx-pm] I'm lost!

[Nick Wehr]

I'm writing an Inline::C module...and I'm getting seg faults when I use it. 
When I run it through valgrind, it tells me that there are memory leaks.  It
says it's from the memory I allocated using Newz from the perl API.  So my
question is this: am I supposed to be using the API functions New, Newz, and
Safefree?  or should I stick with the standard malloc and free?  Here's some
output from valgrind:

==13668== 144672 bytes in 14 blocks are possibly lost in loss record 13 of 14
==13668==    at 0x34149540: malloc (vg_replace_malloc.c:131)
==13668==    by 0x341BD23A: Perl_safesysmalloc (util.c:69)
==13668==    by 0x341C9392: Perl_reentrant_init (reentr.c:143)
==13668==    by 0x3416DC24: perl_construct (perl.c:295)
==13668==
==13668== LEAK SUMMARY:
==13668==    definitely lost: 21290 bytes in 20 blocks.
==13668==    possibly lost:   144672 bytes in 14 blocks.
==13668==    still reachable: 1439929 bytes in 28708 blocks.
==13668==         suppressed: 0 bytes in 0 blocks.


Thanks!


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
http://info.mail.yahoo.com/mail_250