Comment # 16
on bug 10476
from Alex Kirk
Bill was correct on both fronts. Landed now, and it was in fact Frame 412.
Identical crash when running with "-C Default". I didn't think I had made any
config changes on that particular installation.
As for that pointer - invalid as in NULL, or pointing off somewhere wonky in
memory? If the latter, my immediate thought would be to see if the value
retrieved looks like it came from that frame, because if that's the case, it's
most likely exploitable.
You are receiving this mail because:
- You are watching all bug changes.
