Closed zeltrax00 closed 1 year ago
Thank you for the report. I'll have a look and see if this is a problem I can fix.
@zeltrax00 I cannot reproduce. It appears you replace the original Symbol in XXXX+0x2ca34:
with XXXX
. If I understand correctly, the cause of the issue is that this Symbol is not handled correctly. In order for me to fix this, I will need to know what the original symbol looks like.
If you do not want to paste the Symbol publicly here on Github, you can email it to me at BugId@skylined.nl.
It is just a DLL from my friend's project, if you need to check I will send the binary package to your email.
I am sure you understand that I will not run arbitrary binaries sent to me by people I do not know out of safety concerns.
If you can just tell me if you replaced the XXXX
in the output and what the original value was, that would be more helpful.
XXXX = BkZlib. It is my friend's custom DLL. I don't know what information you can get from that
The root cause is that the real symbol follows a pattern I am not handling correctly. I cannot fix this unless I know what that symbol looks like.
The problem is caused by a line in disassembly generated by cdb.exe
. In your initial report it says that line was b'XXXX+0x2ca34:'
. This looks like a line containing a symbol, which the code should handle in line 90. The code grbSymbolLine.match(sbDisassemblyOutputLine)
should match, so the code inside the if statement on line 91 and following should not be executed. This means that an exception on line 93 is impossible if the symbol was b'XXXX+0x2ca34:'
. The symbol cannot be b'BkZlib+0x2ca34:'
either; that would also match on line 90 and never execute line 93.
Please provide the original, unaltered bug report created by BugId. It has all the information I need to fix this.
@SkyLined This is the original bug report 2022-11-29 15։24։50.725336 BugId error report #14.txt
Thank you. It appears that this is something I already fixed: https://github.com/SkyLined/mBugId/commit/504bd2924ef685e3192de4409f5a6d1c97e07327
To get this fix, you can either get the latest version of BugId/mBugId through git, download the latest version of fo0GetDisassemblyForProcessAndCdbCommand.py into the folder modules\mBugId\mDisassembler
, or wait for the next release.
I did indeed not need to know the full symbol; that was a red herring. I was looking at the latest code, which does not have this issue, which is why I could not understand how you were seeing this assertion. I thought you were obfuscating some complex symbol which cause an issue in the latest code, which is why I asked for the full symbol.
Thank you, I use the lastest version of mBugId then the problem is gone
Thank you again for the report and confirming the issue is fixed!
I don't know what it is, but it says that I can create a new issue here