You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by ax...@ws.apache.org on 2004/10/15 12:45:51 UTC

[jira] Closed: (AXISCPP-179) SIGSEGV when Entry/Exit trace embedded and enabled

Message:

   The following issue has been closed.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-179

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-179
    Summary: SIGSEGV when Entry/Exit trace embedded and enabled
       Type: Bug

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Axis-C++

   Assignee: 
   Reporter: Andrew Perry

    Created: Thu, 30 Sep 2004 2:52 AM
    Updated: Fri, 15 Oct 2004 3:44 AM
Environment: Linux

Description:
When the Axis client libraries have been built with entry and exit trace added, and tracing is enabled by including the ClientLogPath entry in the axiscpp.conf, a 404 error causes the client to through a SIGSEGV. Under normal circumstances the tracing works correctly. With tracing embedded in the code, but not enabled the client behaves as expected with this error.

Debug info:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1221623680 (LWP 12639)]
0xb7395e29 in free () from /lib/tls/libc.so.6
(gdb) bt
#0  0xb7395e29 in free () from /lib/tls/libc.so.6
#1  0xb7391abb in _IO_free_backup_area_internal () from /lib/tls/libc.so.6
#2  0xb7390060 in _IO_new_file_overflow () from /lib/tls/libc.so.6
#3  0xb7390ab0 in _IO_new_file_xsputn () from /lib/tls/libc.so.6
#4  0xb7385332 in fputs () from /lib/tls/libc.so.6
#5  0xb75a8ed0 in axiscpp::AxisTrace::logthis (this=0x80543a8, sLog=0xbfffbf30 "> SoapKeywordMapping::uninitialize()",
    level=3, arg2=0xb75c976c "/home/andyp/cwssBuild/obj/src/soap/SoapKeywordMapping.cpp", arg3=131) at AxisFile.h:106
#6  0xb75a9026 in axiscpp::AxisTrace::logaxis (this=0x80543a8, sLog=0xbfffbf30 "> SoapKeywordMapping::uninitialize()",
    level=3, arg2=0xb75c976c "/home/andyp/cwssBuild/obj/src/soap/SoapKeywordMapping.cpp", arg3=131)
    at /home/andyp/cwssBuild/obj/src/common/AxisTrace.cpp:159
#7  0xb759c0c6 in axiscpp::SoapKeywordMapping::uninitialize ()
    at /home/andyp/cwssBuild/obj/src/soap/SoapKeywordMapping.cpp:131
#8  0xb757fbb9 in uninitialize_module () at /home/andyp/cwssBuild/obj/src/engine/Axis.cpp:351
#9  0xb7582d4d in ~Call (this=0x80533d0) at /home/andyp/cwssBuild/obj/src/engine/client/Call.cpp:98
#10 0xb7565bb6 in ~Stub (this=0xbfffc310) at /home/andyp/cwssBuild/obj/src/engine/client/Stub.cpp:102
#11 0x0804a4d4 in ~MathOps (this=0xbfffc310)
    at /home/andyp/cwssBuild/obj/test/generated/cpp/ExceptionTest/MathOps.cpp:43
#12 0x0804b980 in main (argc=2, argv=0xbfffc524)
    at /home/andyp/cwssBuild/obj/test/generated/cpp/ExceptionTest/ExceptionTestClient.cpp:94

As the error appears to be thrown from within fputs(), I'm guessing that there is a memory leak somewhere and it's overwriting the trace memory.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira