Re: [osol-discuss] SIGSEGV in libc.so.1`_malloc_unlockedonSolarisx86machine

2008-01-03 Thread Frank Hofmann
: [EMAIL PROTECTED]; opensolaris-discuss@opensolaris.org Subject: Re: [osol-discuss] SIGSEGV in libc.so.1`_malloc_unlockedonSolarisx86machine Hi I have tried LD_PRELOAD and UMEM_DEBUG with my program on Sparc. Everything worked. I also am unable to find any bug in my program. No clue as to who

Re: [osol-discuss] SIGSEGV in libc.so.1`_malloc_unlockedonSolarisx86machine

2008-01-02 Thread Vamsee Priya
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, December 27, 2007 2:48 PM To: Vamsee Priya Cc: [EMAIL PROTECTED]; opensolaris-discuss@opensolaris.org Subject: Re: [osol-discuss] SIGSEGV in libc.so.1

Re: [osol-discuss] SIGSEGV in libc.so.1`_malloc_unlockedonSolarisx86machine

2007-12-27 Thread Frank . Hofmann
-discuss] SIGSEGV in libc.so.1`_malloc_unlockedonSolarisx86machine On Wed, 26 Dec 2007, Vamsee Priya wrote: Hi, From the umem_status I too agree that some thing in my program corrupted the memory. I am working on as to what caused the problem. The same program works fine always in SPARC

Re: [osol-discuss] SIGSEGV in libc.so.1`_malloc_unlockedonSolarisx86machine

2007-12-27 Thread Casper . Dik
Hi I have tried LD_PRELOAD and UMEM_DEBUG with my program on Sparc. Everything worked. I also am unable to find any bug in my program. No clue as to who is the culprit.. You will need to go over your code and check it carefully. Something is copying a few extra bytes into a structure. (Note

Re: [osol-discuss] SIGSEGV in libc.so.1`_malloc_unlockedonSolarisx86machine

2007-12-26 Thread Vamsee Priya
, 2007 6:52 PM To: Vamsee Priya Cc: [EMAIL PROTECTED]; opensolaris-discuss@opensolaris.org Subject: Re: [osol-discuss] SIGSEGV in libc.so.1`_malloc_unlockedonSolarisx86machine On Wed, 26 Dec 2007, Vamsee Priya wrote: Hi, From the umem_status I too agree that some thing in my program corrupted