Re: How to debug "received fatal signal"

On 04/19/2014 02:07 PM, Wouter Beek wrote:
> The third time I run my program the message is again different. Included on
> an external site because of its length:
> htttp://www.wouterblog.com/error3.log
> 
> On Sat, Apr 19, 2014 at 1:25 PM, Beek, W.G.J. <[email protected]> wrote:
> 
>> > For completeness' sake I here include another crash of the same program:
>> >
>> > ~~~
>> > *** glibc detected *** swipl: munmap_chunk(): invalid pointer:
>> > 0x00007ffee9b59080 ***
>> > ======= Backtrace: =========
>> > /lib64/libc.so.6[0x3266876166]
>> >
>> > /home/wbk440/lib/swipl-7.1.11/lib/x86_64-linux/libswipl.so.7.1.11(+0xc402b)[0x7ffff7d9902b]
>> >
>> > /home/wbk440/lib/swipl-7.1.11/lib/x86_64-linux/libswipl.so.7.1.11(+0xc421c)[0x7ffff7d9921c]
>> >
>> > /home/wbk440/lib/swipl-7.1.11/lib/x86_64-linux/libswipl.so.7.1.11(+0xc471c)[0x7ffff7d9971c]

Looks like memory corruption.  With this information it is very hard to
say anything
more sensible about it.  The presented addresses depend on the exact
details on how
Prolog was compiled.  You can change this line in the `build` script:

   # export COFLAGS="-O2 -gdwarf-2 -g3"

into

   export COFLAGS="-gdwarf-2 -g3"

run a `make distclean` and ./build.  That makes the system possibly
about twice as
slow (on CPU bounded tasks), but might give a little more insight.

The best you can typically do to help is create test case that can be
reproduced.

	Cheers --- Jan