Generate MachO format dumps by the MacOS createdump #48664
Assignees
Labels
area-Diagnostics-coreclr
enhancement
Product code improvement that does NOT require public API changes/additions
Milestone
Comments
mikem8361
added
enhancement
|
Tagging subscribers to this area: @tommcdon Issue DetailsCurrently createdump generates ELF core dumps on MacOS. We need to develop a MachO dump writer for the VS for Mac conversion to .NET Core.
|
dotnet-issue-labeler
bot
added
the
untriaged
18 tasks
mikem8361
added a commit
to mikem8361/runtime
that referenced
this issue
Apr 12, 2021
Instead of the hacky ELF core dumps on MacOS now createdump generates true MachO dumps. Setting the COMPlus_DbgEnableElfDumpOnMacOS environment variable is no longer needed. Add special thread info memory region containing the OS thread ids missing from macho core dumps. This allows SOS to map the thread indexes to thread ids. The address (0x7fffffff00000000) of this special memory region is above the highest user address (0x0007FFFFFFFFF000) and below a kernel reserved address (0xffffff8000xxxxxx) which is kind of moot because dumps don't include any kernel regions. lldb seems just fine with this memory region. The changes include ARM64 support also, but since I don't have a M1 device I can't build/test them. I'm hoping Steve can at least review them. Add --verbose/TRACE_VERBOSE support to tone down all the macho dump generation spew. Issue: dotnet#48664
ghost
pushed a commit
that referenced
this issue
Apr 15, 2021
* Add MachO dump writer to createdump Instead of the hacky ELF core dumps on MacOS now createdump generates true MachO dumps. Setting the COMPlus_DbgEnableElfDumpOnMacOS environment variable is no longer needed. Add special thread info memory region containing the OS thread ids missing from macho core dumps. This allows SOS to map the thread indexes to thread ids. The address (0x7fffffff00000000) of this special memory region is above the highest user address (0x0007FFFFFFFFF000) and below a kernel reserved address (0xffffff8000xxxxxx) which is kind of moot because dumps don't include any kernel regions. lldb seems just fine with this memory region. The changes include ARM64 support also, but since I don't have a M1 device I can't build/test them. I'm hoping Steve can at least review them. Add --verbose/TRACE_VERBOSE support to tone down all the macho dump generation spew. Issue: #48664 * Fix build problem * Update docs * Code review feedback Co-authored-by: Juan Sebastian Hoyos Ayala <juhoyosa@microsoft.com>
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently createdump generates ELF core dumps on MacOS. We need to develop a MachO dump writer for the VS for Mac conversion to .NET Core.
The text was updated successfully, but these errors were encountered: