NoneType object has
verd1c opened this issue · comments
LLDB Version: 18.1.1
Platform: x64 Windows 11
Python: Python 3.13.0a5
It seems that on Windows 11 the flag register becomes None at some point before printing
Hi @verd1c
Many thanks for raising this as an issue and your proposed fix. While the fix worked fine when I tested on Windows I've opted to do a wider refactor around the handling of flags registers to:
- Provide better error handling if the flags register isn't exposed by LLDB on whatever platform (i.e. will not display the nonetype exception)
- Support defining multiple flag variables with differing bitmasks in the arch files.
PR up at #25 - If you have some time I'd be really appreciative if you would be able to test that branch on your specific environment and let us know if it works as expected.
Hey @stephen-f0,
PR #25 seems to work fine on my environment:
Thanks a lot for fixing! I'll close this now
Thank you for testing - That fix is now in main