Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=598160 --- Comment #12 from Petr Pisar <ppisar@xxxxxxxxxx> 2010-06-17 04:31:17 EDT --- If explicit form->DESTROY() is called, it is killed by glibc because Newt::Form::Destroy → Newt::newtFormDestroy($self->{co}) → XS_Newt_newtFormDestroy → newtFormDestroy(co) → free() is called twice on the same co. First time by explicit DESTROY, second time by Perl on object destruction (second time `co' structure members points to different memory and thus it's killed by glibc or kernel depending on target address). I checked newt C library and there are no checks for NULL pointers, any free() is not followed by assigning NULL to freed pointer. Thus it's application (perl-Newt) responsibility not use destroyed newt components. However I don't understand the Perl XS magic. Thus I can not say what's bad in perl-Newt XS wrapper now. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/perl-devel
