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. -- Regards, Vadym Krevs -----Original Message----- From: Rajib Majumder [mailto:rajibm2005@gmail.com] Sent: Sun 9/3/2006 2:31 PM To: suse-amd64@suse.com Subject: [suse-amd64] Porting from SLES9/EM64T SLES9/AMD64 Hi, After porting a C++ application from SLES9/EM64T architecture to SLES9/AMD64, it fails to work. Apparently, looks like a stack corruption is happening. It works perfect on SLES9/EM64T arch. Any idea what might have gone wrong? Env is same on both boxes and gcc used was 3.3.2 to build the application. Any input is highly appreciated. Thanks Rajib ********************************************************************** 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.