ModelInference / texada

Efficient techniques for mining LTL formulae over linear input traces

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

texadatest terminates with segfault and MapCheckerTest.ResourceAllocation test fails

bestchai opened this issue · comments

Running texadatest I get one non-deterministic test failure. That is, sometimes this test passes and sometime it fails:

texadatest(40303,0x7fff79d58310) malloc: *** mach_vm_map(size=2372415452829274112) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[ FAILED ] MapCheckerTest.ResourceAllocation (14 ms)

Also, the texadatest printout ends with a segfault:
"Segmentation fault: 11"

[Issue created by bestchai: 2014-07-14]

[Comment created by carolemieux: 2014-07-14]
I think I fixed the hard-coded paths in the most recent revision, but it requires setting up an environment variable (as in the above comment).

[Comment created by bestchai: 2014-07-14]
Oh, I didn't realize that this could be a symptom of hardcoded paths. Let me re-run once you have a fix for that and see if this is still an issue.

[Comment created by bestchai: 2014-07-14]
Works for me after setting TEXADA_HOME. Yes, need to document, probably best to add this to the README.md file.

[Comment created by carolemieux: 2014-07-14]
Strange that it would pass at all, actually, since it used hard-coded paths. Did you change the file paths in the code?

I wasn't able to replicate the std::bad_alloc exception message. However I did get a segfault when the file path was wrong.

I've started by making the tests machine independent, see rev dbb9735. This requires setting the environment variable:

TEXADA_HOME

to the location of the texada location (i.e. folder storing traces/), starting with a forward slash and w/o another forward slash at the end, e.g.:

TEXADA_HOME=/home/clemieux/workspace/texada/Texada

That should help if you didn't change the file paths. Of that's not it, I'll look further.