https://bugs.kde.org/show_bug.cgi?id=364058
--- Comment #6 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
(In reply to Sergey Meirovich from comment #5)
> Sorry. I indeed missed that. But why next also doesn't trigger any error
> message?
>
> -bash-4.1$ cat t.c
> int main(int c, char **o)
> {
> int stack[2];
> stack[0] = c;
> stack[1] = c++;
> stack[2] = c++;
> return stack[2];
> }
exp-sgcheck associates (for each function call) each instruction to the first
array accessed
by this instruction. It then checks that (during the same function call) this
instruction continues to access the same array (and in the array bounds).
So, basically, this means that exp-sgcheck will only detect array over or
under-run in
loops. It will never detect an over/under-run on instructions executed only
once
(either because they are not in a loop, or because the loop is executed once).
All this limitations derived from the fact that exp-sgcheck works at binary
level. It has
to discover which array is accessed by an instruction 'at run time'.
--
You are receiving this mail because:
You are watching all bug changes.
