-
Notifications
You must be signed in to change notification settings - Fork 565
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
browser_tests hangs with drcov tool on Linux #1390
Comments
From [email protected] on March 17, 2014 09:19:08 Tried different options:
|
From [email protected] on March 17, 2014 12:16:30
22365: (gdb) info threads
(gdb) thread 2 0x46d7d190: mov $0x23,%eax 22367:
(gdb) where 22368:
22393:
22413
(gdb) x/60gx $rbp 0x712f96fc <terminate_via_kill+102>: mov %rax,%rdi So it may came from the cleanup_and_terminate |
From [email protected] on March 17, 2014 12:43:53 more on 22413 (gdb) info threads
(gdb) x/30gx 0x4d0aeb58 (gdb) x/50i 0x712aaf9d calling from terminate_via_kill dcontext->sys_param0: 0xf dcontext: 0x000000004d05ea80 |
From [email protected] on March 17, 2014 13:04:40 (gdb) x/300gx 0x4d0aeb58 0x712f97f5 <terminate_via_kill_from_anywhere+98>: callq 0x712f9696 <terminate_via_kill> 0x712fa980 <execute_default_action+3166>: callq 0x712f9793 <terminate_via_kill_from_anywhere> 0x711b59c0 <heap_free+90>: callq 0x711b4a0e <common_heap_free> 0x712fb1e8 <execute_default_from_dispatch+44>: callq 0x712f9d22 <execute_default_action> 0x712f9377 <execute_handler_from_dispatch+2303>: callq 0x712fb1bc <execute_default_from_dispatch> 0x712fb64f <receive_pending_signal+1120>: callq 0x712f8a78 <execute_handler_from_dispatch> |
From [email protected] on March 27, 2014 12:05:15 If remove the SIGTERM and only keep SIGKILL, the test won't hang, but still fail.
process 13845 and 13846 are children of 13828, which is a child process of 13808. |
From [email protected] on March 27, 2014 15:50:29 -no_nudge_kills has the same problem, so at least there are problems without soft_kills. static bool |
From [email protected] on April 03, 2014 14:36:34 By replacing the event_exit with dump data only, there is no hang. |
From [email protected] on April 03, 2014 14:37:34 In drcov, on pre-execve-syscall, we should iterate over all thread and dump data in the case of drcov_per_thread. |
From [email protected] on April 03, 2014 14:39:17 On pre-execve-syscall, we dumped the coverage data. However, the execve test may fail, and we may dump the coverage data to the same file again later. |
From [email protected] on April 03, 2014 15:06:09 Re: execve failing: it may be better to handle this in the client. execve failing is not uncommon (some apps just try execve with each component on path instead of a separate check for existence), and if you have a large app run a lot of code and then do 30 failing execves you're going to have an enormous logfile. |
From [email protected] on April 04, 2014 10:02:50 This issue was closed by revision r2632 . Status: Fixed |
From [email protected] on April 04, 2014 11:09:08 Keep it open as there are still a few issues to be fixed. Status: Accepted |
From [email protected] on March 13, 2014 17:05:33
/home/zhaoqin/Workspace/DynamoRIO/builds/build_x64_dbg.git/bin64/drrun -debug -checklevel 1 -disable_traces -c /home/zhaoqin/Workspace/DynamoRIO/builds/build_x64_dbg.git/clients/lib64/debug/libdrcov.so -- ./out/Release/browser_tests --no-sandbox --gtest_filter=AppListStartPageWebUITest.Basic --ui-test-action-max-timeout=80000000 --ui-test-action-timeout=40000000
Attach to 9451, 9453, stop at nop after syscall
Attach to 9490, 9510, loop at debug_infinite_loop
It runs fine without drcov client
Original issue: http://code.google.com/p/dynamorio/issues/detail?id=1390
The text was updated successfully, but these errors were encountered: