axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samisa Abeysinghe <samisa.abeysin...@gmail.com>
Subject Re: Need Help Installing axis-c for Linux
Date Fri, 07 Oct 2005 22:36:19 GMT
Michael Kipper wrote:

>--- Samisa Abeysinghe <samisa.abeysinghe@gmail.com> wrote:
>
>  
>
>>Well I am not a gdb guru, hence not that sure with attaching, may be you 
>>could watch variables as well as back trace.
>>
>>    
>>
>
>I rebuilt axis-c with trace and debug.
>
>  
>
>>However what I do is:
>>
>>[root@lfs ~/blfs]# gdb httpd
>> and then on gdb promt run:
>>(gdb) r -X
>>
>>then run a cliet, and if the server crashes gdb will drop back to gdb
>>prompt. Then run:
>>(gdb) bt
>>
>>    
>>
>
>Here goes:
>[root@lfs ~]# set +h
>[root@lfs ~]# PATH=/opt/apache/sbin:/usr/bin:/bin gdb httpd
>GNU gdb 6.3
>Copyright 2004 Free Software Foundation, Inc.
>GDB is free software, covered by the GNU General Public License, and you
>are
>welcome to change it and/or distribute copies of it under certain
>conditions.
>Type "show copying" to see the conditions.
>There is absolutely no warranty for GDB.  Type "show warranty" for details.
>This GDB was configured as "x86_64-pc-linux-gnu"...(no debugging symbols
>found)
>Using host libthread_db library "/lib64/libthread_db.so.1".
>
>(gdb) r -X
>Starting program: /opt/apache/sbin/httpd -X
>(no debugging symbols found)
>(no debugging symbols found)
><snip>
>(no debugging symbols found)
>(no debugging symbols found)
>[Thread debugging using libthread_db enabled]
>[New Thread 46912516256144 (LWP 4728)]
>(no debugging symbols found)
>(no debugging symbols found)
><snip>
>(no debugging symbols found)
>(no debugging symbols found)
>Program received signal SIGSEGV, Segmentation fault.
>[Switching to Thread 46912516256144 (LWP 4728)]
>0x00002aaaae789ad6 in XercesHandler (this=0x63fc30) at AxisTrace.h:194
>194         static inline bool isTraceOn() { return
>(*g_traceEntrypoints->m_traceOn)(); }
>Current language:  auto; currently c++
>(gdb) bt
>#0  0x00002aaaae789ad6 in XercesHandler (this=0x63fc30) at AxisTrace.h:194
>#1  0x00002aaaae78e0f8 in XMLParserXerces (this=0x63fc10)
>    at /obj/src/xml/xerces/XMLParserXerces.cpp:40
>#2  0x00002aaaae78fc9b in CreateInstance (inst=0x7fffffb8edc0)
>    at /obj/src/xml/xerces/ParserLoader.cpp:36
>#3  0x00002aaaae208529 in axiscpp::XMLParserFactory::getParserObject ()
>   from /opt/apache/modules/libaxis_server.so
>#4  0x00002aaaae21785b in axiscpp::WSDDDocument::parseDocument ()
>   from /opt/apache/modules/libaxis_server.so
>#5  0x00002aaaae21794d in axiscpp::WSDDDocument::getDeployment ()
>   from /opt/apache/modules/libaxis_server.so
>#6  0x00002aaaae1f16fd in axiscpp::WSDDDeployment::loadWSDD ()
>   from /opt/apache/modules/libaxis_server.so
>#7  0x00002aaaae20b7d8 in initialize_module ()
>   from /opt/apache/modules/libaxis_server.so
>#8  0x00000000004277ea in ap_run_child_init ()
>#9  0x0000000000425a5d in ap_graceful_stop_signalled ()
>#10 0x0000000000425fb4 in ap_graceful_stop_signalled ()
>#11 0x0000000000426743 in ap_mpm_run ()
>#12 0x000000000042d210 in main ()
>(gdb)
>
>  
>
>>One more thing; are the Xerces libs on a location that could be located
>>by Apache?
>>    
>>
>
>[root@lfs ~]# /sbin/ldconfig -v | grep xerces
>/opt/xerces-c/lib:
>        libxerces-depdom.so.26 -> libxerces-depdom.so.26.0
>        libxerces-c.so.26 -> libxerces-c.so.26.0
>
>  
>
OK, it seems that the problem is with the parser.
However it is strange that it says that it is failing in trace:  
AxisTrace.h:194
I am not sure whay this is. May be you could disable trace and try gdb.
We have had few problems with Xerces 2.6 in the past. I am not sure if 
this is one of those. The alternative is to try with Xerces 2.2.

Thanks,
Samisa...

>Thanks again,
>Michael
>
>
>  
>


Mime
View raw message