You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like while the main process's module has proper address metadata in a minidump, at least some dynamic libraries don't. For example, I have a minidump produced by the diskwrite example pulling in #42. The top frame of its call stack should be __psynch_cvwait in libsystem_kernel.dylib, but the base_of_image value reported for the libsystem_kernel.dylib module is 0x1802ed000 - too small. It looks like there's no ASLR on this module for some reason, so I used LLDB on a separate run and it reports the base address as 0x18e935000. That lines up properly with the instruction pointer at the start of the thread's stack frame in the minidump.
It looks like while the main process's module has proper address metadata in a minidump, at least some dynamic libraries don't. For example, I have a minidump produced by the diskwrite example pulling in #42. The top frame of its call stack should be
__psynch_cvwait
inlibsystem_kernel.dylib
, but thebase_of_image
value reported for the libsystem_kernel.dylib module is0x1802ed000
- too small. It looks like there's no ASLR on this module for some reason, so I used LLDB on a separate run and it reports the base address as0x18e935000
. That lines up properly with the instruction pointer at the start of the thread's stack frame in the minidump.Here's the dump of this module:
And the register state of the thread:
And the full minidump: minidump.tar.gz
The text was updated successfully, but these errors were encountered: