Hi I thought that the bug might be in my program. But everything works fine with 64 bit binary....are there any flags that need to be set/unset while compling? And I reiterate that things worked fine some times with the 32 bit binary also....
Thanks Priya -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, December 26, 2007 5:59 PM To: Vamsee Priya Cc: [email protected] Subject: Re: [osol-discuss] SIGSEGV in libc.so.1`_malloc_unlocked onSolarisx86 machine >Hi >Apart from the scenario I explained below, I also get a SIGABRT with the >following stack trace > >libc.so.1`_lwp_kill+0x15(1, 6) >libc.so.1`raise+0x1f(6) >libumem.so.1`umem_do_abort+0x25(9, fefb5000, 804691c, fef98b1c, >fefa3ae8, 80aa810) >libumem.so.1`umem_err_recoverable+0x46(fefa3ae8) >libumem.so.1`umem_error+0x453(1, 80aa810, 80c7c68) >libumem.so.1`umem_free+0xf6(80c7c68, 50) >libumem.so.1`process_free+0xfd(80c7c70, 1, 0, 80469a8, 805890b, 80c7c70) >libumem.so.1`free+0x14(80c7c70, 80c1b48, 0, 80c1b60) >meta_free+0xbf(80469f0, 80c1b88, 1, 80a0bd0, 0, 0) >active_out+0x44e(6, 8047e1f, 0, 65) >active+0xe0(2, 8047e1f, 0, 0, 8046b57) >main+0xd59(6, 8047d0c, 8047d28) >_start+0x80(6, 8047dd8, 8047df7, 8047dfa, 8047e0c, 8047e1f) > >Please suggest me as to what can be done to over come these issues. Fix the bug in your program :-) This is a abort() from libumem which indicates that it found an error in your program. So you need to take the core from SIGABRT and run that with "mdb". Casper _______________________________________________ opensolaris-discuss mailing list [email protected]
