SIGABRT crashing a process

[dewasi]

Hi Johnathan,
                   Thanks for the comments,Sending the stack in a bit more
detail , i am a bit new to unix/linux, would appreciate any help or pointer
from your side.

(gdb) bt
#0  0xffffe402 in __kernel_vsyscall ()
#1  0x003c0df0 in raise () from /lib/libc.so.6
#2  0x003c2701 in abort () from /lib/libc.so.6
#3  0x003f928b in __libc_message () from /lib/libc.so.6
#4  0x004015a5 in _int_free () from /lib/libc.so.6
#5  0x004019e9 in free () from /lib/libc.so.6
#6  0x006f4581 in operator delete(void*) () from /usr/lib/libstdc++.so.6
#7  0xf6a40d61 in SStringList::Pop() () from /u0/imail2/pmail/lib/libomu.so
#8  0xf6a40e37 in SStringList::Shift() () from
/u0/imail2/pmail/lib/libomu.so
#9  0xf6b73049 in getDbSvcLine (body=..., key=...) at sc_netdb.cxx:729
#10 0xf6b7337e in sc_gethostbyname_r (name=0x9c23f98 "rwc-qe03-v1",
he=0xf4532e60, hd=0xf4530d20) at sc_netdb.cxx:801
#11 0xf6b3a81a in snimGetIpAddrFromName (hostname=0x9c23f98 "rwc-qe03-v1",
addrbuf=0x9c200b4 "", addrbufsz=46) at ostcp.cxx:865
#12 0xf6b3b3c3 in swcom_host2ip (name=0x9c23f98 "rwc-qe03-v1",
output=0x9c200b4 "") at ostcp.cxx:1225
#13 0xf6f445b8 in ldap_open_default_connection (ld=0x9b47f18) at open.c:108
#14 0xf6f4e506 in send_server_request (ld=0x9b47f18, ber=0x9c1bf98, msgid=1,
parentreq=0x0, srvlist=0x0, lc=0x0, bind=0) at request.c:129
#15 0xf6f4e480 in send_initial_request (ld=0x9b47f18, msgtype=96,
dn=0x97cbe0c "cn=root", ber=0x9c1bf98) at request.c:105
#16 0xf6f4c4eb in ldap_simple_bind (ld=0x9b47f18, dn=0x97cbe0c "cn=root",
passwd=0x97cbedc "secret") at sbind.c:99
#17 0xf6f4c54e in ldap_simple_bind_s (ld=0x9b47f18, dn=0x97cbe0c "cn=root",
passwd=0x97cbedc "secret") at sbind.c:121
#18 0xf7210b72 in LdapConnection::initialize (this=0x9c1bf70) at
LdapConnection.cpp:44
#19 0xf7214752 in LdapConnectionManager::obtainLdapConnection
(this=0x97cbc50) at ldapConnectionManager.cpp:130
#20 0xf7212436 in loadAccountFromDirectory (filter=0xf7219d13 "mailboxid=",
value=0x9c1c21d "334394530", dn=0x0, ldapErrors=@0xf453381b)
    at loadAccountData.cpp:323
#21 0xf7212f5a in loadAccountFromDirectoryByMailboxID (accountid=0x9c1c21d
"334394530", bLdapErrors=@0xf453381b) at loadAccountData.cpp:532
#22 0xf746932a in Pmail::VMSS::sendJMSNotification (this=0x96c7338,
id=0x9c1c21d "334394530", message=..., event=New) at VMSS.cpp:1062
#23 0xf746b070 in Pmail::VMSS::createMessage (this=0x96c7338, id=0x9c1c21d
"334394530", foldername=0x9c1c234 "/INBOX", message=...) at VMSS.cpp:674
#24 0xf7455253 in Pmail::handleCreateMessage(PushEmail::VMSS *, ._81 *, ._82
*) (theVMSS=0x96c7338, rctxt=0x9b3a5c8, wctxt=0x9b39ba0)
    at CmdHandlers.cpp:324
#25 0xf744f9d5 in vmssServerHandle(._208 *, ._209 *) (rctxt=0x9b3a5c8,
wctxt=0x9b39ba0) at mod_vmss.cpp:199
#26 0xf744fe87 in ob_proto_dispatch (r=0xf45340c4, data=0x9c1c1e0
"Requests", dataLen=9211) at mod_vmss.cpp:271
#27 0xf74503d0 in VMSSModule_handler (r=0xf45340c4) at mod_vmss.cpp:360
#28 0xf7fc362c in ap_invoke_wildcard_handler (hl=0x96bbccc, str=0x9c2400d
"/vmss", r=0xf45340c4) at ap_module.cxx:846
#29 0xf7fc3943 in ap_invoke_handler (r=0xf45340c4) at ap_module.cxx:873
#30 0xf7fd65fd in ServerFunc (c=0x96c06e8) at server.cxx:670
#31 0x080753bf in ConnProcess (c=0x96c06e8) at conn.cxx:185
#32 0xf7fd5a5b in ServerAcceptNoOSA (threadArgs=0x96c06e8) at
server.cxx:1053
#33 0x00514832 in start_thread () from /lib/libpthread.so.0
#34 0x00469e0e in clone () from /lib/libc.so.6

Thanks
-Dewasi



Jonathan Wakely-4 wrote:
> 
> On 19 January 2011 13:04, dewasi wrote:
>>
>> Hi,
>> I have an application where multiple processes talk to each other.One of
>> the
>> process is crashing repeatedly via a SIG ABRT signal, I have tried to put
>> in
>> a gdb on that process and tried to figure out what the stack is at the
>> point
>> of the crash.the stack kinda looks like this at the time of SIG ABRT:
>> Code:
>>
>> (gdb) bt
>> #0  0xffffe402 in __kernel_vsyscall ()
>> #1  0x006cbc10 in raise () from /lib/libc.so.6
>> #2  0x006cd521 in abort () from /lib/libc.so.6
>> #3  0x00701c5b in __libc_message () from /lib/libc.so.6
>> #4  0x007098b6 in _int_free () from /lib/libc.so.6
>> #5  0x0070ce00 in free () from /lib/libc.so.6
> 
> libc has detected an invalid 'free' here, called from...
> 
>> #6  0x008e0691 in operator delete () from /usr/lib/libstdc++.so.6
> 
> called from ...
> 
>> #7  0xf6a92d61 in SStringList::Pop ()
>> #8  0xf6a92e37 in SStringList::Shift ()
>> #9  0xf6bc5049 in getDbSvcLine
>> #10 0xf6bc537e in sc_gethostbyname_r
>> #11 0xf6b8c81a in snimGetIpAddrFromName
>> #12 0xf6b8d3c3 in swcom_host2ip
>> #13 0xf6f965b8 in ldap_open_default_connection
>> #16 0xf6f9e4eb in ldap_simple_bind
>> #17 0xf6f9e54e in ldap_simple_bind_s
>> #18 0xf7212b72 in LdapConnection::initialize
>> #19 0xf7216752 in LdapConnectionManager::obtainLdapConnection
>> #21 0xf7214f5a in loadAccountFromDirectoryByMailboxID
>>
>>
>> WOULD APPRECIATE ANY POINTER which can help in understanding or working
>> around this SIGABRT.MY guess is something is going bad with the
>> initialize
>> method.
> 
> Usually this indicates a 'double delete' i.e. freeing something twice.
> Or maybe you are trying to delete an uninitialized pointer.
> 
> You should build with debugging symbols to see exactly which line the
> error occurs on, and you could try running the app under valgrind to
> track down the memory errors.
> 
> 

-- 
View this message in context: http://old.nabble.com/SIGABRT-crashing-a-process-tp30707259p30746095.html
Sent from the gcc - libstdc++ mailing list archive at Nabble.com.