Closed moyix closed 2 years ago
Thanks! I'm converting that list into a checklist so we can mark them off here as we believe they're resolved so you can test and confirm. I'm going through them again after a few recent optimization and bug fixes to see what's left. I suspect that a few of the lager ones are likely OOMs and am curious how they do with the new memory improvements.
FWIW, my repro step was to simply add an extra print at the end and if I saw that print assume there was no crash. Let me know if you forsee any problems with that
I mentioned it elsewhere but for anyone else tracking it, that only one left unchecked is likely an invalid function anyway? The offset aligns with a mangled string name it looks like.
Not sure if you've had a chance to re-run this with recent dev builds, curious if you've been able to reproduce what we're seeing as all these being resolved.
Version and Platform (required):
Bug Description:
Recently I used Binary Ninja to collect IL and Pseudo-C for ~5 million functions across 80K binaries from Debian. This exposed a number of segfaults. I'm reporting them in bulk here because unfortunately I don't have time to go through and try to figure out which ones are unique.
Note that although the binaries have DWARF info, I didn't try to use the DWARF plugin with them; this is a clean install of BN.
Steps To Reproduce:
Expected Behavior:
Binary Ninja should not segfault ;)