On Sat, Aug 20, 2016 at 11:01:19AM -0400, Lincoln A Baxter via RT wrote:
Show quoted text> Can you show me the output of:
>
> perl -MConfig -e 'print $Config{archname} ."\n" ;'
>
armv6j-linux
I have now Linux-4.4.11, gcc-5.4.0, glibc-2.22, perl-5.22.2 and
Sys-SigAction-0.22. The t/nested.t from Sys-SigAction-0.22 still segfaults.
Show quoted text> Also I have attached a rewritten nested.t that allows one to
> control both the depth of nesting and the number of iterations.
> Can you run this first without arguments (as in):
>
> perl -Ilib t/nested.t
>
> On your platform (if I guessed the archname string right) is will default to
> a depth of 2 and 2 iterations. Please show me the out if it segfaults.
>
> Then can you run it with different depths set (as in):
>
> perl -Ilib t/nested.t 5 1 #depth of 5, 1 iteration
> perl -Ilib t/nested.t 5 1 #depth of 4, 1 iteration
> perl -Ilib t/nested.t 5 1 #depth of 3, 1 iteration
> perl -Ilib t/nested.t 5 1 #depth of 1, 1 iteration
>
None of them (5 1, 4 1 etc.) segfaults with the new t/nested.t. I tried
different depths and iterations.
Show quoted text> Because this works fine on all the POSIX (unix) platforms the smoke testers
> have tested on, the I suspect this is a problem with the underlying signal
> handling in perl on ARM platforms.
I also suspect a bug in the perl.
Show quoted text> So, if you want this port of perl fixed, you'll want to get
> a stack trace from the core file resulting from the segfault and file a bug
> against this perl port.
>
The stack trace is unusable because after the crash, the debuger reports the
last two frames are identical so the stack is corrupted.
-- Petr