You may be right. I guess it's how one defines stack corruption. From valgrind's manual: 3.1. Kinds of bugs that Memcheck can find ... * Reading/writing inappropriate areas on the stack ... -- Regards, Vadym Krevs -----Original Message----- From: Andi Kleen [mailto:ak@suse.de] Sent: Mon 9/4/2006 12:02 AM To: suse-amd64@suse.com Cc: Vadym Krevs; Rajib Majumder Subject: Re: [suse-amd64] Porting from SLES9/EM64T SLES9/AMD64 On Sunday 03 September 2006 16:22, Vadym Krevs wrote:
I'd try valgrind'ing your application. Install the latest valgrind*.rpm and then run your application under valgrind - this will pinpoint any dodgy memory accesses/operations in the application.
valgrind can't diagnose stack corruptions unfortunately (except for use of uninitialized data), only heap issues. -Andi -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.