I too think that it is not the place that it is crashing. We have to
locate the place where it is corrupting memory.
Samisa...
Raghavendra SM wrote:
Isn't that just reflecting that the process has been killed?
I can't any programming error being detected in that. Please correct me
if wrong.
Regards,
~raghav
-----Original Message-----
From: Senaka Fernando [mailto:[EMAIL PROTECTED]
Sent: Monday, March 10, 2008 1:02 PM
To: Apache AXIS C User List
Subject: RE: Core dumps in Axis libraries
Found it!
==22786== Process terminating with default action of signal 15 (SIGTERM)
==22786== at 0x403760E: accept (in /lib/tls/libpthread-2.3.6.so)
==22786== by 0x44C2CF2: axis2_http_svr_thread_run
(http_svr_thread.c:128)
==22786== by 0x44C28D4: axis2_http_server_start (http_receiver.c:227)
==22786== by 0x44DA92E: axis2_transport_receiver_start
(transport_receiver.c:41)
==22786== by 0x8084D3C: axis_init(int, char**)
(http_server_main.cpp:155)
==22786== by 0x8059896: main (sps_server.h:159)
Regards,
Senaka
Manjula,
This was with out my logs enabled.
Regards,
~raghav
-----Original Message-----
From: Manjula Peiris [mailto:[EMAIL PROTECTED]
Sent: Monday, March 10, 2008 12:58 PM
To: Apache AXIS C User List
Subject: RE: Core dumps in Axis libraries
Is this valgrind report is when your log level increased or not ? If
yes
then can you try valgrind without increasing the log level.
-Manjula.
On Mon, 2008-03-10 at 12:39 +0530, Raghavendra SM wrote:
When I tried the Valgrind, it doesn't point to any obvious clues
atleast. It doesn't show any "definitely lost" or "indirectly lost"
blocks. Though, there are some "still reachable" and "possibly lost"
blocks.
Please find the attached valgrind report. Please let me know if the
valgrind is revealing something here?
Thanks & Regards,
~raghav
-----Original Message-----
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2008 7:07 PM
To: Apache AXIS C User List
Subject: Re: Core dumps in Axis libraries
Raghavendra SM wrote:
Thanks Folks,
I'm attaching the server log during the crash. Also, the first
back-trace in the dump.log points to dump with guthilla=yes.
The attached dump does not lead to a clue on what is going wrong. It
looks to me as if there is some or the other memory corruption
somewhere. I hope valgrind would lead to a clue.
Thanks,
Samisa...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Samisa Abeysinghe
Software Architect; WSO2 Inc.
http://www.wso2.com/ - "Oxygenating the Web Service Platform."
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
