[Arch Linux] mapa2lts-* segfault about ltsmin HOT 2 CLOSED

Plus: this seems to be an incorrect stack frame. If you compile ltsmin with
-O0 and -g then you see a different frame which is probably the right one.
Note also that the segfault may occur at a random level if you do not use
those options.
Op 15 okt. 2014 15:24 schreef "Dennis Guck" [email protected]:

Executing mapa2lts-* results into a segfault under Arch Linux. This is my
output by gdb:

[...]
mapa2lts-dist: No output, just counting the number of states
mapa2lts-dist: level 0 has 1 states, explored 0 states 0 transitions
mapa2lts-dist: reward label 0=

Program received signal SIGSEGV, Segmentation fault.
dm_project_vector (m=0x69b780 , row=4, src=src@entry=0x1, tgt=tgt@entry=0x7fffffff9960)
at dm.c:1377
1377 tgt[k++] = src[i];
(gdb) bt
#0 dm_project_vector (m=0x69b780 , row=4, src=src@entry=0x1, tgt=tgt@entry=0x7fffffff9960)
at dm.c:1377
#1 #1 0x000000000042d6c2 in
project_dest (context=0x7fffffffdbc0, ti=0x7fffffff99e0, dst=0x1, cpy=0x0)
at pins.c:140
#2 0x0000000000407a25 in prcrl_callback () at mapa-pins.c:170
#3 0x00007ffff7a268da in cdjp_info () from
/usr/local/lib/ltsmin-2.0/libscoop.so
#4 0x0000000000000004 in ?? ()
#5 0x00007ffff2416d30 in ?? ()
#6 0x00007ffff4723fc0 in ?? ()
#7 0x00007ffff6215672 in stg_newPinnedByteArrayzh () from
/usr/lib/ghc-7.8.3/rts-1.0/libHSrts_thr-ghc7.8.3.so
#8 0x0000ff000000ff00 in ?? ()
#9 0x0000000000000000 in ?? ()
(gdb) bt
#0 dm_project_vector (m=0x69b780 , row=4, src=src@entry=0x1, tgt=tgt@entry=0x7fffffff9960)
at dm.c:1377
#1 #1 0x000000000042d6c2 in
project_dest (context=0x7fffffffdbc0, ti=0x7fffffff99e0, dst=0x1, cpy=0x0)
at pins.c:140
#2 0x0000000000407a25 in prcrl_callback () at mapa-pins.c:170
#3 0x00007ffff7a268da in cdjp_info () from
/usr/local/lib/ltsmin-2.0/libscoop.so
#4 0x0000000000000004 in ?? ()
#5 0x00007ffff2416d30 in ?? ()
#6 0x00007ffff4723fc0 in ?? ()
#7 0x00007ffff6215672 in stg_newPinnedByteArrayzh () from
/usr/lib/ghc-7.8.3/rts-1.0/libHSrts_thr-ghc7.8.3.so
#8 0x0000ff000000ff00 in ?? ()
#9 0x0000000000000000 in ?? ()

—
Reply to this email directly or view it on GitHub
#1.

from ltsmin.

We have merged Stefan's commits. This is fixed now.

from ltsmin.