SIGABRT crashing a process

[dewasi]

Hi Jonathan,
                 Thanks for your comments. It helps but being a bit  new to
linux/unix world I am unable to guage how to build the application with
debugging symbols in the make file.I am aware of how to do stuff using
Valgrind but have not done anything using debugging symbols. Can you throw
in some guidance.It would be very helpfull.

Thanks
-Piyush



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-tp30707259p30745943.html
Sent from the gcc - libstdc++ mailing list archive at Nabble.com.