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
hey all, i noted that when doing a default dump of a remote linux process only the stack of the current thread is captured but not anything else and so i've found that i have had to manually enumerate all the memory mappings for a given process and call https://docs.rs/minidump-writer/latest/minidump_writer/minidump_writer/struct.MinidumpWriter.html#method.set_app_memory in order for them to be dumped, i know this makes sense but i was curious if it would be desirable to automate this process as apart of the crate? similar to how you can choose a full minidump when dumping a remote process on windows? i'd be happy to submit a PR if interested
The text was updated successfully, but these errors were encountered:
hey all, i noted that when doing a default dump of a remote linux process only the stack of the current thread is captured but not anything else and so i've found that i have had to manually enumerate all the memory mappings for a given process and call https://docs.rs/minidump-writer/latest/minidump_writer/minidump_writer/struct.MinidumpWriter.html#method.set_app_memory in order for them to be dumped, i know this makes sense but i was curious if it would be desirable to automate this process as apart of the crate? similar to how you can choose a full minidump when dumping a remote process on windows? i'd be happy to submit a PR if interested
The text was updated successfully, but these errors were encountered: