when you can use valgrind - most other things are pretty useless.
did you encounter a memory-handling bug that valgrind failed to catch,
while another tool (such as libsafe) did catch?
note: i never used libsafe, so i might be missing something - i simply
compared valgrind to many other avai
Hi Valery,
I do use valgrind to find memory leaks, but libsafe suppose to directly
get me the name of function where stack is smashed.
I forgot to write, that in order to disable GCC stack protectin, I
compile my application and libsafe with -fno-stack-protector option.
Valery Reznic wro
You can try to use valgrind.
Valery
--- On Sun, 5/18/08, Lev Olshvang <[EMAIL PROTECTED]> wrote:
> From: Lev Olshvang <[EMAIL PROTECTED]>
> Subject: Corrupted stack - Why Ubuntu 7.10 does not have libsafe; does not
> show errors in ?
> To: "linux-il"
> Date: Sunday, May 18, 2008, 4:47 PM
>
Hi people,
I am fighting with stack corruption problem in my appilcation
I wanted to use libsafe , but debian/ubuntu packages are not accessible,
so I built libsafe manually from source tar distribution
And now, I see from trace ouput that altough my calls are indeed
intercepted in preloaded