New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault not catched #2
Comments
I haven't, but then I have never dealt with RcppDeepState in the past as well. I know of a few common situations with DeepState where you aren't properly compiling the Test Harness (like simply appending the option to explicitly link the library using -ldeepstate) or executing the binary produced thereafter, but those appear to not be the case here. From what I can grasp of the situation, I'd suggest to check the configurations of the machines you are running on (assuming this worked liked you said in one machine, otherwise if it didn't I'd run Valgrind and debug for accesses. And if it is segfaulting, there would be no output file yes). And from what you mentioned, I can't tell what system this is being run on or what's the other 'different machine' that it worked on, but there could be noticeable inconsistencies across platforms. |
Finally, I came up with something interesting: the output files are now created, and Valgrind produces an I'm going to explore a little more into this. Thanks @Anirban166 ! |
Anytime, good to see you exploring! |
I've finally figured out the answer! The issue was that the library's shared object was built without the Solved in #3 |
I was trying to run RcppDeepState on the test package provided in the
/inst/testSAN
on a different machine.First of all I ran the test harness compilation procedure
deepstate_harness_compile_run
and it succesfully generated the compiled test harness. After that I ran thedeepstate_harness_analyze_pkg
function and no matter how many times I ran the function, no bug was reported for thetestSAN
package.After some investigation, I discovered that no output file was generated for each Test Harness. For example: the output folder for
rcpp_use_after_deallocate
function located attestSAN/inst/testfiles/rcpp_use_after_deallocate/rcpp_use_after_deallocate_output
was empty. So I attempted to run the Test Harness execution manually. What I discovered is that before the output file is generated, the Test Harness gives me a segmentation failure error.Is there something I'm overlooking? The program appears to crash in the try-catch block, without actually catching the error.
Executing the test on a different machine works perfectly: it catches the errors and saves the test case in the output directory.
@Anirban166 have you ever dealt a situation like this with DeepState?
The text was updated successfully, but these errors were encountered: