Segmentation fault (core dumped) on uniform example

[GoogleCodeExporter]

Segmentation fault (core dumped) on uniform example

[GoogleCodeExporter]

Right, I have this same problem, too. It happens both on fedora 15 & debian 
wheezy when using 'infer' in alchemy-2. But when I run 'liftedinfer' there is 
no problem anymore.

Original comment by [email protected] on 12 Mar 2013 at 7:24

[GoogleCodeExporter]

Same here. Here is valgrind output: 

:~/alchemy/alchemy-2/bin$ valgrind ./infer -i base.mln -r 
uniform.result -e empty.db -q Heads

==8431==    at 0x8073311: Clause::getPredicate(int const&) const (clause.h:301)
==8431==    by 0x819AB45: buildInference(Inference*&, Domain*&, bool const&, 
Array<Predicate*>&, Array<TruthValue>&) (infer.h:1257)
==8431==    by 0x819CAD8: main (infer.cpp:620)
==8431==  Address 0x8 is not stack'd, malloc'd or (recently) free'd
==8431== Process terminating with default action of signal 11 (SIGSEGV)
==8431==  Access not within mapped region at address 0x8
==8431==    at 0x8073311: Clause::getPredicate(int const&) const (clause.h:301)
==8431==    by 0x819AB45: buildInference(Inference*&, Domain*&, bool const&, 
Array<Predicate*>&, Array<TruthValue>&) (infer.h:1257)
==8431==    by 0x819CAD8: main (infer.cpp:620)
==8431==  If you believe this happened as a result of a stack
==8431==  overflow in your program's main thread (unlikely but
==8431==  possible), you can try to increase the size of the
==8431==  main thread stack using the --main-stacksize= flag.
==8431==  The main thread stack size used in this run was 8388608.
==8431== 
==8431== HEAP SUMMARY:
==8431==     in use at exit: 79,569 bytes in 509 blocks
==8431==   total heap usage: 1,017 allocs, 508 frees, 116,164 bytes allocated
==8431== 
==8431== LEAK SUMMARY:
==8431==    definitely lost: 0 bytes in 0 blocks
==8431==    indirectly lost: 0 bytes in 0 blocks
==8431==      possibly lost: 13,251 bytes in 48 blocks
==8431==    still reachable: 66,318 bytes in 461 blocks
==8431==         suppressed: 0 bytes in 0 blocks
==8431== Rerun with --leak-check=full to see details of leaked memory
==8431== 
==8431== For counts of detected and suppressed errors, rerun with: -v
==8431== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Segmentation fault (core dumped)


So the problem occurs at line 301 of clause.h file. (the predicate[idx] is 
invalid read)

Original comment by [email protected] on 20 Aug 2013 at 8:36

[GoogleCodeExporter]

Same problem here

Original comment by [email protected] on 15 Sep 2014 at 7:36

[GoogleCodeExporter]

Does anyone know how to solve this problem?

Original comment by [email protected] on 10 Oct 2014 at 1:10