> reliably. But it relies upon being able to determine the frame limits
> of strcpy()'s caller. So -fomit-frame-pointer will, it appears, stop it
> working. Vendors (Mandrake at least) are currently shipping
> frame-pointerless shared libs.
The frame pointer is not a safe way to find the end of a buffer. You can
easily have
char buf[256];
void *ptr;
in the stack frame and indirectly overwrite ptr without going out of the
frame. Since the code then writes to ptr you can do a two step buffer
overrun.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Apr 21 2000 - 08:32:05 EDT