ansaurus

Question

ActiPerl + Tcl.pm *** glibc detected *** munmap_chunk(): invalid pointer: 0x09b5e0d8

Answer 1

A:

You should not need this line: use lib "/opt/ActivePerl-5.10/lib"; unless you have a misconfiguration. You might want to nuke the install from orbit and start over.

Is there any particular reason why you are using ActivePerl? You should be able to simply install perl from source -- you're using a real OS, so I'd take advantage of it :)

Ether 2010-06-25 16:21:50

Answer 2

A:

First stage analysis: memory corruption on exit. I'd say that there's warring over who should free a block and how. Now we dig deeper…

It's possible that you're seeing the consequences of the fact that both Perl and Tcl are independently trying to work around the ~~bugs~~ misfeatures in the system implementation of environment variables. In particular, the C library's setenv() has a number of problems with memory leaks which make it rather more impractical than you might naïvely expect; I'd quite expect Perl to work around this, and I know that Tcl does too, but it does mean that only one language should set environment variables, and that almost certainly needs to be Perl in this case (on the basis of evidence you've presented).

Do you really need to set environment variables from your Tcl code? If you can just not do it, that'd be the easiest way forward. :-) Otherwise, we're talking about having a different build of Tcl (so that it asks the Perl side of things to do the memory management) or doing some magic to disconnect the Tcl side from the real environment. You might also want to report the problem upstream to ActiveState.

Donal Fellows 2010-06-26 20:44:52

Answer 3

A:

I'll keep digging and if I find the solution I'll let you know. I reported this to ActiveState. Inline is my email and their response, but to sum up:

1. They didn't develop "Inline Tcl" for Perl nor did they test it.
2. It was developed in 2001 and no additions were made to it since then.
3. When it was developed (in 2001), it was marked as "alpha" and no additions were made since then.



Hi Mircea,

Inline::Tcl is not part of ActivePerl. It's not tested with ActivePerl, and it
does not build on our PPM build farm against ActivePerl:
http://ppm4.activestate.com/i686-linux/5.10/1000/R/RR/RRS/Inline-Tcl-0.09.d/log-20090614T112213.txt

Offhand, the error message looks like a compiler mismatch problem, but it could be
almost anything since Inline::Tcl hasn't been touched by the author since 2001,
and even then the release notes describe it as "alpha software". It doesn't seem
to like Linux very much any more:
http://matrix.cpantesters.org/?dist=Inline-Tcl%200.09;maxver=1
Hmm.. The author's home page is 404. You should probably find another way to do it.

Mircea 2010-06-28 08:38:53

ansaurus

tags:

views:

answers:

ActiPerl + Tcl.pm * glibc detected * munmap_chunk(): invalid pointer: 0x09b5e0d8

related questions