-
Notifications
You must be signed in to change notification settings - Fork 263
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
release build perturb_only test failure on Linux #1516
Comments
From [email protected] on April 08, 2014 14:16:04 When run DrM release and DR debug build:
<Initial options = -no_dynamic_options -logdir '/tmp/Dr. Memory/dynamorio' -client_lib '/usr/local/google/home/zhaoqin/Workspace/DrMemory/builds/build_x86_drm_rel.git/bin/release/libdrmemorylib.so;0; After the Stopping printout, it takes awhile to exit, or not even exit. (gdb) where (gdb) x/20i 0x46c1e8e1 So it is a thread with inserted clean call do_delay. So it is more likely the delay took so long so often that it is hard to reach a safe place for DR to handle the signal and do proper exit. |
From [email protected] on April 09, 2014 09:41:47 If skip the syscall for dr_delay, we still see the test hang, where every threads hang at mutex lock system call. Every caller is at dynamo_thread_exit_common on line 2251: static int |
From [email protected] on April 09, 2014 09:48:42 (gdb) x/60x $esp (gdb) x/x 0xf716d284 (gdb) info threads
|
From [email protected] on April 08, 2014 17:11:33
The following tests FAILED:
43 - perturb_FLAKY (Failed)
Errors while running CTest
It only happens in release build
Original issue: http://code.google.com/p/drmemory/issues/detail?id=1516
The text was updated successfully, but these errors were encountered: