axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nadir amra (JIRA)" <>
Subject [jira] Commented: (AXISCPP-237) dlopen failures should show reason for failure
Date Thu, 06 Jan 2005 02:01:13 GMT
     [ ]
nadir amra commented on AXISCPP-237:

I think there is a bug in the usage of dlerror.  The function dlerror will either return NULL
or a string...the string is in a static buffer.  So when we throw AxisEngineException, passing
in the value returned by dlerror(), the AxisEngineException::processException routine tries
to delete the buffer passed in if non-null, which is not correct. 

This issued should probably be reopened.

> dlopen failures should show reason for failure
> ----------------------------------------------
>          Key: AXISCPP-237
>          URL:
>      Project: Axis-C++
>         Type: Improvement
>  Environment: All
>     Reporter: Andrew Perry
>     Priority: Minor

> When a dlopen() error occurs a message like "DLOPEN FAILED in loading parser library"
is exception message thrown. For problem determination it would be much more beneficial to
output the reason for failure too, i.e. the output of dlerror().
> The AxisEngineException code already has support for this, but it hasn't been implemented
in XMLParserFactory.cpp, SOAPTransportFactory.cpp or HandlerLoader.cpp, where a dlerror()
can just be added to the throw AxisEngineException statement.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message