----- "Ken McDonell" <kenj@xxxxxxxxxxxxxxxx> wrote:
> I've almost finished libpcp_import and the Perl wrapper, but one
> issue has me stumped.
>
> My test program in C works fine (as in run under the control of
> valgrind without errors).
>
> The functionally identical Perl program dies when perl_destruct() is
> called as perl finishes and aborts on a bad call to free(). The
> valgrind version of the failure is
Sounds like something is corrupting the Perl interpreters stack - I
imagine its going to be in LogImport.xs ... could you either send it
(all) over, or do an in-progress git commit to your dev branch & I'll
take a closer look.
> Does anyone on the list know enough about the guts of Perl to help me
> understand how to get control over, or debug, what perl_destruct() is
> trying to do?
I suspect its a victim. perl_destruct is part of the perl API - its
tearing down the interpreter right at the end of execution (its also
executed as part of every perl invocation, ever, so has good chance
of not being the cause here).
cheers.
--
Nathan
|