-
Notifications
You must be signed in to change notification settings - Fork 110
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
Errors due to mapped memory #30
Comments
How I wrote dsdump, I'll mmap the executable into memory, but I needed a way to ensure I don't mix up the load addresses of the binary with dsdump's own address space. I chose 0x400000000 as a place where not a lot of code lives. You can submit a fix via a PR, modify this location if you were to build yourself, or give me the |
|
If you use macOS Monterey (12)+, try to run the old released $ MallocNanoZone=0 dsdump --objc dsdump For details, see my comment at #35 (comment). |
Hey @ynyyn thanks for the PR! I can confirm your build works fine on
|
Anyone had similar issues? The error message references to
mmap()
mostly on Google. My memory is free (no apps open), other apps are not recalling the issue with memory. What else can it be?The text was updated successfully, but these errors were encountered: