Comment # 19
on bug 10476
from Pascal Quantin
(In reply to Alex Kirk from comment #18)
> You do realize that non-null pointers that are "wrong" are how arbitrary
> code execution happens, right?
Yes I do...
> I've ready the TRY/ENDTRY block and I admit to not understanding where
> exactly in the C the issue is occurring. Are we talking the Catch for the
> OutOfMemory error, or is there some other thing implied in that block?
No it does not happen in the CATCH block but in the ENDTRY macro as explained
in comments 14 and 17.
You are receiving this mail because:
- You are watching all bug changes.
