# The following was supposedly scribed by
# Eric Wilhelm
# on Sunday 11 July 2004 01:11 pm:
>>Can someone please tell me what wrong?
>
>I can't say exactly what went wrong, but I get the same results on my
> machine (except for the summary.)
(aside: this runs flawlessly on my gentoo box with Python 2.2.3 and perl,
v5.8.0 built for i686-linux)
Okay, seems to be a string-copy issue, but there are segfaults from other
issues that I'm not sure I understand. Below is a report for some of the
tests showing the line which causes the segfault and, in paretheses, why I
think it happens.
(running Python 2.3.4 and perl 5.8.3 built for i386-linux-thread-multi)
01testpl.t
perl.py_eval("print 'Wow. Now that is weird'")
* Segmentation fault (?)
02testpl.t
o.foof({'neil': 1}, ['laura', 1], 12)
* Segmentation fault (?)
03parse.t
print perl.Data.Dumper.Dumper({'neil': "happy", 'others': "sad"})
* Segmentation fault (Python string passed to perl as hash value)
o = perl.Parse.RecDescent.new("Parse::RecDescent","dumb: 'd' 'u' 'm' 'b'")
* Segmentation fault (Python string "Parse::RecDecent" passed to perl)
05JAxH.t
unless JAxH('Inline')
* Segmentation fault (Python string return to perl)
06dict.t
$obj->set_data({string => 'hello',
* Segmentation fault (perl string passed to python)
07nherit.t
$obj->set_data({string => 'hello',
* Segmentation fault (perl string passed to python)
ok($obj->add("wink"), "hellowink");
* Segmentation fault (perl string passed to python)
ok($obj->takeaway("fiddle"), "hel");
* Segmentation fault (perl string passed to python)
08ipyobj.t
my $r = $o->get("neil");
* Segmentation fault (perl string passed to python)
$r = py_call_method($o, 'get', "neil");
* Segmentation fault (perl string passed to python)
END REPORT
Is this something to do with python and perl not using the same malloc?
--Eric
--
"It works better if you plug it in!"
--Sattinger's Law
