Hi All
When I use my 32 bit binary on Solaris x86 machine, I get a segmentation
fault with the following stack trace.
libc.so.1`_malloc_unlocked+0x14c(4000, 3, 80a3130, 1, 8046a38, 805763f)
libc.so.1`malloc+0x39(4000, 0, 8046a1c, fef9e455, fef9158c, 4)
meta_del+0x13(2, 80a3100, 10, 0)
: Re: [osol-discuss] SIGSEGV in libc.so.1`_malloc_unlocked on
Solaris x86 machine
Hi All
When I use my 32 bit binary on Solaris x86 machine, I get a
segmentation
fault with the following stack trace.
libc.so.1`_malloc_unlocked+0x14c(4000, 3, 80a3130, 1, 8046a38, 805763f)
libc.so.1`malloc+0x39(4000
On Mon, 24 Dec 2007, [EMAIL PROTECTED] wrote:
Hi
I don't find a core dump generated when a SIGSEGV is received. I set the
LD_PRELOAD variable to watchmalloc.so.1 but could not find the actual
place of seg. fault as the core dump file is not generated. (I got the
stack trace I pasted when I
Hi All
When I use my 32 bit binary on Solaris x86 machine, I get a segmentation
fault with the following stack trace.
libc.so.1`_malloc_unlocked+0x14c(4000, 3, 80a3130, 1, 8046a38, 805763f)
libc.so.1`malloc+0x39(4000, 0, 8046a1c, fef9e455, fef9158c, 4)
meta_del+0x13(2, 80a3100, 10, 0)
Vamsee Priya wrote:
Hi All
When I use my 32 bit binary on Solaris x86 machine, I get a segmentation
fault with the following stack trace.
libc.so.1`_malloc_unlocked+0x14c(4000, 3, 80a3130, 1, 8046a38, 805763f)
libc.so.1`malloc+0x39(4000, 0, 8046a1c, fef9e455, fef9158c, 4)
meta_del+0x13(2,
