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 05:46:51 UTC
[jira] Created: (AXISCPP-204) Client segfaults when trying to call methods of caught exception
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-204
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-204
Summary: Client segfaults when trying to call methods of caught exception
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis-C++
Components:
Basic Architecture
Versions:
1.3 Beta
Assignee:
Reporter: Samisa Abeysinghe
Created: Thu, 14 Oct 2004 8:45 PM
Updated: Thu, 14 Oct 2004 8:45 PM
Environment: Linux with axis2 transport and Xerces parser
Description:
I have the following code in my client:
catch (AxisException & e)
{
int code = e.getExceptionCode();
cout << "e.getExceptionCode()" << code << endl;
printf ("Exception : %s\n", e.what ());
return -1;
}
The client segfaults when e.getExceptionCode() is called.
If I comment that line, then the client craches when e.what() is called.
Also I observed that exception class has:
virtual const char* what() const throw();
However AxisException class that inherits exception class has:
virtual const char* what() throw() = 0;
Note that trailing const is missing in the second call. I guess this is a bug.
---------------------------------------------------------------------
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
[jira] Closed: (AXISCPP-204) Client segfaults when trying to call methods of caught exception
Posted by ax...@ws.apache.org.
Message:
The following issue has been closed.
Resolver: Samisa Abeysinghe
Date: Mon, 18 Oct 2004 9:00 PM
Damitha's fix on AxisTransportException class has fixed this problem.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-204
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-204
Summary: Client segfaults when trying to call methods of caught exception
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Axis-C++
Components:
Basic Architecture
Fix Fors:
1.3 Final
Versions:
1.3 Beta
Assignee:
Reporter: Samisa Abeysinghe
Created: Thu, 14 Oct 2004 8:45 PM
Updated: Mon, 18 Oct 2004 9:00 PM
Environment: Linux with axis2 transport and Xerces parser
Description:
I have the following code in my client:
catch (AxisException & e)
{
int code = e.getExceptionCode();
cout << "e.getExceptionCode()" << code << endl;
printf ("Exception : %s\n", e.what ());
return -1;
}
The client segfaults when e.getExceptionCode() is called.
If I comment that line, then the client craches when e.what() is called.
Also I observed that exception class has:
virtual const char* what() const throw();
However AxisException class that inherits exception class has:
virtual const char* what() throw() = 0;
Note that trailing const is missing in the second call. I guess this is a bug.
---------------------------------------------------------------------
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