forwarded 680116 http://www.swi-prolog.org/bugzilla/show_bug.cgi?id=45 thanks
Hello, Thanks for the backtrace. I forwarded your bug report to the above address. Please add any missing details there. BTW you could try to upload logol to experimental and set build-deps to require swi-prolog 6.0.2. I cannot upload swi-prolog to unstable now, because it does not build on sparc and mipsel. Regards, Eugeniy Meshcheryakov 4 липня 2012 о 16:40 +0200 olivier sallou написав(-ла): > Here are gdb logs: > > Program received signal SIGSEGV, Segmentation fault. > 0x400000000007ce21 in into_relocation_chain () > (gdb) backtrace > #0 0x400000000007ce21 in into_relocation_chain () > #1 0x4000000000088370 in garbageCollect () > #2 0x400000000008a3a0 in ensureGlobalSpace () > #3 0x4000000000046170 in PL_next_solution () > #4 0x4000000000010360 in main () > > I also attach strace log. > > Standard output: > .... > [c,c,c] > getchars > gotchars > [c,c,c] > getchars > gotchars > [c,c,c] > getchars > gotchars > Segmentation fault > > For debug I have put a write before and in predicate call, with a sleep(1) > to be sure to print the statement in output. > The seg fault occured before putting those write/sleep and always occurs at > the same time in the present test. > > -- > > gpg key id: 4096R/326D8438 (keyring.debian.org) > > Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
signature.asc
Description: Digital signature
