Your message dated Fri, 12 Oct 2012 00:30:50 +0200
with message-id <[email protected]>
and subject line Re: Bug#680116: swi-prolog: seg fault on Sparc and IA64
has caused the Debian Bug report #680116,
regarding swi-prolog: seg fault on Sparc and IA64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
680116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680116
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Version: 6.2.2-13
I see logol was built without errors in experimental, so I'm closing
this bug for this branch.
Regards.
Eugeniy Meshcheryakov
11 жовтня 2012 о 00:22 +0200 Eugeniy Meshcheryakov написав(-ла):
> Hello Olivier,
>
> Could you try to build logol with swi-prolog >= 6.2.2-13 (in
> experimental). There are quite a lot of fixes for various crashes and
> data corruption in this version.
>
> Regards,
> Eugeniy Meshcheryakov
>
> 1 серпня 2012 о 12:16 +0200 olivier sallou написав(-ла):
> > I have uploaded logol to experimental, but it still fails the same way on
> > IA64 (same issue).
> >
> > New release introduced an errorin my build, I had to patch my code (an
> > error that was supported at prolog code load, but now raising an error).
signature.asc
Description: Digital signature
--- End Message ---
