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
1. Any way to filter the type/text of a CLR Exception?
Currently I can filter a .NET CLR exception (inside an event handler) by using:
if (code == win32.EXCEPTION_DEBUG_EVENT and event.get_exception_code() == 0xE0434352):
, but I cannot figure out how to "dig" inside the .NET exception (similar to !PrintException or !pe with the SOS.dll in WinDbg) to filter further on its text/type/etc.
2. Any way to generate a WinDbg/Visual Studio compatible .dmp full memory dump file (similar to .dump /ma in WinDbg, for example)?
I know I can use crash.fetch_extra_data( event, takeMemorySnapshot = 2 ) , but I am not sure how to convert the result to a .dmp file.
Any pointers will be greatly appreciated.
The text was updated successfully, but these errors were encountered:
As for your questions: I've only implemented the raw Win32 part of it all, so there's currently no support for digging into .NET exceptions or generating WinDbg dumps. Been meaning to implement the second one for a while but I never seem to find the time.
Winappdbg is a great tool!
I have a couple of questions:
1. Any way to filter the type/text of a CLR Exception?
Currently I can filter a .NET CLR exception (inside an event handler) by using:
if (code == win32.EXCEPTION_DEBUG_EVENT and event.get_exception_code() == 0xE0434352):
, but I cannot figure out how to "dig" inside the .NET exception (similar to !PrintException or !pe with the SOS.dll in WinDbg) to filter further on its text/type/etc.
2. Any way to generate a WinDbg/Visual Studio compatible .dmp full memory dump file (similar to .dump /ma in WinDbg, for example)?
I know I can use
crash.fetch_extra_data( event, takeMemorySnapshot = 2 )
, but I am not sure how to convert the result to a .dmp file.Any pointers will be greatly appreciated.
The text was updated successfully, but these errors were encountered: