[omniORB] catching BAD_PARAM is not working...
renny.koshy at rubixinfotech.com
renny.koshy at rubixinfotech.com
Mon Dec 20 18:10:13 GMT 2004
On solaris 8, Forte compiler, I have a problem catching BAD_PARAM from
omniORB:
The following code is in thrad 'n'... (simplified -- removed all other
catch blocks for testing)
fprintf(stderr,"%s:%d\n", __FILE__, __LINE__);
fflush(stderr); /// this is line 409 in the trace output below
try {
CORBA::Object_var obj =
ORB->string_to_object( Buffer );
fprintf(stderr,"%s:%d\n", __FILE__,
__LINE__); fflush(stderr);
T.SQLAgent =
GSQL::SQLAgent::_narrow(obj);
fprintf(stderr,"%s:%d\n", __FILE__,
__LINE__); fflush(stderr);
} catch(CORBA::BAD_PARAM& ex) {
Worker->error("Connection attempt -
Caught system exception BAD PARAM -- unable to contact the object.");
}
This never seems to catch the BAD_PARAM exception...
Here's the output:
../Database/GenericSQL.cpp:409
Run-time exception error; current exception: BAD_PARAM
No handler for exception.
signal fault in critical section
signal number: 11, signal code: 2, fault address:
0xfd802000, pc: 0xfe8da6dc, sp: 0xfdf0dc18
libthread panic: fault in libthread critical section : dumping core (PID:
15051 LWP 3)
stacktrace:
fe8da6c0
fe8dd6a0
fe8dd730
fe8eb01c
fe8dd6d8
./startgk: line 30: 15051 Segmentation Fault (core dumped) EXSKernel
$*
Please help!
Renny Koshy
President & CEO
--------------------------------------------
RUBIX Information Technologies, Inc.
www.rubixinfotech.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20041220/941d4851/attachment-0001.htm
More information about the omniORB-list
mailing list