2012/7/3 Eugeniy Meshcheryakov <[email protected]> > Hello, > > Could you please try to reproduce the bug with swi-prolog 6.0.2 from > experimental? A gdb backtrace and/or last lines of output from ltrace > and/or > strace would also be useful. >
I can't test with experimental package. I build IA64 on debian servers and adm cannot install experimental package. I gonna try for the trace. Olivier > > Regards, > Eugeniy Meshcheryakov > > 3 липня 2012 о 19:44 +0200 Olivier Sallou написав(-ла): > > Package: swi-prolog > > Version: 5.10.4-3 > > Severity: important > > > > Dear Maintainer, > > * What led up to the situation? > > My package logol fails to build on IA64 and Sparc, some tests are > failing while ok on other archs > > * What exactly did you do (or not do) that was effective (or > > ineffective)? > > I analysed the reason of failing tests and found that a seg fault > occurs during the treatment > > * What was the outcome of this action? > > Basically, I parse a file, extract some chars at a position and do > some treatment. On those archs, > > I end with a segmentation fault always at the same "time". I added > some logs and it appears it occurs when > > calling a predicate. I added a write as first instruction of the > predicate and it is not executed. Could be a > > memory allocation issue? See sample log below > > * What outcome did you expect instead? > > Treatment should be as on other archs > > > > A sample exec output below, the search at is the position in file. It > fails at 24, which is not the end of file. > > > > > > search ccc at 2 > > [c,c,c] > > getchars > > gotchars > > search ccc at 3 > > [c,c,c] > > getchars > > gotchars > > search ccc at 4 > > [c,c,c] > > getchars > > gotchars > > search ccc at 5 > > [c,c,c] > > getchars > > gotchars > > search ccc at 6 > > [c,c,c] > > getchars > > gotchars > > .... > > search ccc at 21 > > [c,c,c] > > getchars > > gotchars > > search ccc at 22 > > [c,c,c] > > getchars > > gotchars > > search ccc at 23 > > [c,c,c] > > getchars > > gotchars > > search ccc at 24 > > Segmentation fault > > > > > > Memory usage is low, this is not an out of memory issue. > > I have no core file to give more info. > > The executed prolog is an executable file, compiled to get a full exe > with embedded prolog libs. > > Compiled with: > > swipl-ld -initfile swi-logol.pl -o logol.exe -v logolSwiMain.c > sicstus.pl logol.pl > > > > Again, it works fine with i386, powerpc and amd64. > > > > I can reproduce the issue with my exe and test files, but I can't > reproduce with a single/easy pl file. > > > > Olivier > > > > -- System Information: > > Debian Release: wheezy/sid > > APT prefers unstable > > APT policy: (500, 'unstable'), (500, 'stable') > > Architecture: amd64 (x86_64) > > > > Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > > Shell: /bin/sh linked to /bin/dash > > > > Versions of packages swi-prolog depends on: > > ii swi-prolog-nox 5.10.4-3 > > ii swi-prolog-x 5.10.4-3 > > > > swi-prolog recommends no packages. > > > > Versions of packages swi-prolog suggests: > > pn prolog-el <none> > > ii swi-prolog-doc 5.6.59-1 > > > > -- no debconf information > > > > > -- gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
