om: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of [EMAIL PROTECTED]
> Sent: Wednesday, December 26, 2007 6:36 PM
> To: Vamsee Priya
> Cc: opensolaris-discuss@opensolaris.org
> Subject: Re: [osol-discuss] SIGSEGV in libc.so.1`_malloc_unlocked
> onSolarisx86machine
ginal Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of [EMAIL PROTECTED]
Sent: Wednesday, December 26, 2007 6:36 PM
To: Vamsee Priya
Cc: opensolaris-discuss@opensolaris.org
Subject: Re: [osol-discuss] SIGSEGV in libc.so.1`_malloc_unlocked
onSolarisx86machine
>This is th
>This is the o/p I get with umem_status when I attach mdb to the process
>running.
>
>Status: ready and active
>Concurrency:0
>Logs: (inactive)
>Message buffer:
>umem allocator: redzone violation: write past end of buffer
>buffer=80c7c68 bufctl=80c8ce8 cache: umem_alloc_80
6:20 PM
To: Vamsee Priya
Cc: [EMAIL PROTECTED]; opensolaris-discuss@opensolaris.org
Subject: RE: [osol-discuss] SIGSEGV in libc.so.1`_malloc_unlocked
onSolarisx86machine
On Wed, 26 Dec 2007, Vamsee Priya wrote:
> Hi
> Apart from the scenario I explained below, I also get a SIGABRT with
