Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D dynamorio
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,467
    • Issues 1,467
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 44
    • Merge requests 44
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • DynamoRIO
  • dynamorio
  • Issues
  • #3137
Closed
Open
Issue created Aug 21, 2018 by Derek Bruening@derekbrueningContributor

CRASH on exit from drcachesim -offline

On my Win10 1803 box:

% bin64/drrun -t drcachesim -offline -- suite/tests/bin/simple_app.exe
<Starting application D:\derek\dr\git\build_x64_dbg_tests\suite\tests\bin\simple_app.exe (7472)>
<Initial options = -no_dynamic_options -client_lib 'D:\derek\dr\git\build_x64_dbg_tests/clients/lib64/debug/drmemtrace.dll;0;-offline' -code_api -probe_api -stack_size 56K -max_elide_jmp 0 -max_elide_call 0 -no_inline_ignored_syscalls -native_exec_default_list '' -no_native_exec_managed_code -no_indcall2direct -pad_jmps_mark_no_trace >
Hello, world!
<Stopping application D:\derek\dr\git\build_x64_dbg_tests\suite\tests\bin\simple_app.exe (7472)>
Segmentation fault

The resulting trace is just fine: this seems to be a crash at the very end of cleanup.

In windbg:

dynamorio!global_do_syscall_syscall+0x5:
00000000`153287d9 eb16            jmp     dynamorio!debug_infinite_loop (00000000`153287f1)
0:000> r
rax=000000000000002c rbx=00007ff73293e3a8 rcx=ffffffffffffffff
rdx=0000000000000000 rsi=000000000000002c rdi=000000001554afb8
rip=00000000153287d9 rsp=000000001554afb8 rbp=00007ff73293e3a8
 r8=0000000000000ffe  r9=0000000000000002 r10=0000000000000000
r11=0000000000000202 r12=0000029c1e74cf20 r13=0000000000000000
r14=0000000000000000 r15=0000029c1e74cf28
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
dynamorio!global_do_syscall_syscall+0x5:
00000000`153287d9 eb16            jmp     dynamorio!debug_infinite_loop (00000000`153287f1)
0:000> kn
 # Child-SP          RetAddr           Call Site
00 00000000`1554afb8 00000000`00000000 dynamorio!global_do_syscall_syscall+0x5 [D:\derek\dr\git\build_x64_dbg_tests\core\CMakeFiles\dynamorio.dir\arch\x86\x86.asm.obj.s @ 2209] 

Did not investigate further yet. Online does not have the crash. This is a relatively new setup so I don't know whether this is a regression or sthg that's always been there on win10: the tests seem to pass despite it.

Assignee
Assign to
Time tracking