Closed maxcoderrrr closed 6 months ago
While preparing a pull request for a simple fix for the --jit
command, I noticed that it is already fixed. It's just that the BugId Release (https://github.com/SkyLined/BugId/releases/download/2022-12-12_12.05/BugId.release.2022-12-12.12.05.zip) doesn't have it applied.
The issue is that inside fxGetCurrentJITDebuggerCommandLine.py
, the return oRegistryValue.xValue;
should be return o0RegistryValue.xValue;
This will result in a correct output:
C:\bugid3>BugId.py --jit
┌───[ Current JIT Debugger ]────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ √ JIT debugger: BugId.
│ Arguments: --pause "--pid=%ld" "--handle-jit-event=%ld" --collateral=10 "--reports=C:\Users\admin\BugId reports" --full-dump
└─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
However, the main issue, BugId not being invoked as a JIT debugger, still persists.
Thank you, that works!
I assume you mean that the changes suggested by @h4x-x0r fixed the issue? Based on that assumption, I am closing this issue.
Hi,
As a potential workaround to the issue outlined in https://github.com/SkyLined/BugId/issues/119, I thought I could try to run BugId as a JIT debugger. My idea was to just start the application regularly, and then manually open the file that causes a crash and have BugId attach at that point and perform its analysis.
However, I ran into another issue in that it doesn't launch as expected when a crash is encountered.
The documentation states this:
Accordingly, I used the following command:
My understanding would be that it should now get executed whenever an application crashes, however, this is not the case. For example, if I specify WinDbg or x64debug as the JIT debugger, they get invoked immediately when a crash is triggered. But having BugId configured, nothing happens. I also don't see it being invoked when monitoring with Procmon and Process Explorer.
Similarly, when executing BugId with the
--jit
argument to see the details of the curently installed JIT debugger, I am getting the following exception:The Debugger value (type REG_SZ) inside the registry has it correctly registered:
The affected code from fxGetCurrentJITDebuggerCommandLine.py:
Is there a different way on how I should configure and invoke it?