Hi Bob, Niko,
On Tue, Sep 13, 2016 at 11:15 PM, Bob Friesenhahn
<bfrie...@simple.dallas.tx.us> wrote:
> On Tue, 13 Sep 2016, László Böszörményi wrote:
>> On Tue, Sep 13, 2016 at 10:42 PM, Niko Tyni <nt...@debian.org> wrote:
>>> This package is failing to build on ppc64el, but built successfully
>>> in the past.
>> This is known and working with upstream to find the root cause.
> A backtrace from a core dump is needed.
I'm not that good with gdb, but as a first shot this may give you more idea.
-- cut --
Core was generated by `/usr/bin/perl t/zlib/write.t '.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00000000000bffc8 in ?? ()
[...]
(gdb) thread apply all bt
Thread 1 (Thread 0x3fffb7ff65b0 (LWP 3923)):
#0 0x00000000000bffc8 in ?? ()
#1 0x00000000000bffcb in ?? ()
#2 0x00003fffb796b320 in InitializeLogInfo () at magick/log.c:301
#3 0x00003fffb796c62c in InitializeMagick (path=0x3fffb7bf0708
"Graphics::Magick") at magick/magick.c:1117
#4 0x00003fffb7bf0074 in boot_Graphics__Magick (my_perl=0x10210010,
cv=<optimized out>) at Magick.xs:2064
#5 0x00000000100e1960 in Perl_pp_entersub (my_perl=0x10210010) at pp_hot.c:3272
#6 0x00000000100d8d88 in Perl_runops_standard (my_perl=0x10210010) at run.c:41
#7 0x0000000010046f18 in Perl_call_sv (my_perl=0x10210010,
sv=0x1023ab78, flags=13) at perl.c:2779
#8 0x0000000010049c3c in Perl_call_list (my_perl=0x10210010,
oldscope=<optimized out>, paramList=0x10213248) at perl.c:4995
#9 0x000000001001e3e0 in S_process_special_blocks
(my_perl=0x10210010, floor=39, fullname=0x1023c100 "BEGIN",
gv=0x1023a980, cv=0x1023ab78) at op.c:8916
#10 0x000000001003e028 in Perl_newATTRSUB_x (my_perl=0x10210010,
floor=39, o=<optimized out>, proto=<optimized out>, attrs=<optimized
out>,
block=<optimized out>, o_is_gv=false) at op.c:8845
#11 0x00000000100422b0 in Perl_utilize (my_perl=0x10210010,
aver=<optimized out>, floor=<optimized out>, version=<optimized out>,
idop=<optimized out>,
arg=<optimized out>) at op.c:6069
#12 0x000000001007f784 in Perl_yyparse (my_perl=0x10210010,
gramtype=<optimized out>) at perly.y:351
#13 0x000000001004ee1c in S_parse_body (xsinit=0x1001d490 <xs_init>,
env=0x0, my_perl=0x10210010) at perl.c:2306
#14 perl_parse (my_perl=0x10210010, xsinit=0x1001d490 <xs_init>,
argc=<optimized out>, argv=<optimized out>, env=0x0) at perl.c:1626
#15 0x000000001001d178 in main (argc=<optimized out>, argv=<optimized
out>, env=<optimized out>) at perlmain.c:114
-- cut --
As Perl debug and libc6 debug symbols installed, I don't know which
library / executable may contain points #0 and #1. Maybe log.c itself?
At least the mentioned line in #2 is:
LockSemaphoreInfo(log_semaphore);
> There were no functions added or removed between 1.3.24 and 1.3.25 and not
> interfaces were changed. If 1.3.24 still builds on the build machine, then
> it is possible to test by replacing individual source files in 1.3.25 with
> files from 1.3.24 and seeing when the problem goes away. Since all tests
> are failing, the problematic code would need to be used in initialization,
> or somehow always encountered. Perhaps magick/utility.c would be a good
> starting point.
Yes, 1.3.24 builds fine in the same environment. As previously noted
the broken change happened before 08th of August and it's not the
MAGICK_CACHE_LINE_SIZE value.
Cheers,
Laszlo/GCS
