Closed robmcmullen closed 7 years ago
It seems to happen sometimes when the new segment is smaller than the old segment. Maybe there's a cached value not being updated?
Found the real problem: selecting a group of bytes, then changing the disassembler for that group to something that results in fewer instructions causes there to be extra rows at the end of the table that don't point to valid instructions
I ran into this error when scrolling down a segment to the end:
but haven't been able to reproduce it. I think it had something to do with switching segments? Keeping this stack trace for posterity in case I run into it again.