From: Vít Špinka <>
Date: Mon, 14 Jan 2013 23:44:32 +0100
Message-ID: <>

Just to let you know (and to help anyone on the internet searching for an answer in the future) - the solution was to use an Oracle-certified/supported compiler. In this case, stop using gcc and choose Oracle Solaris Studio instead.


Dne 17.12.2012 23:53, Vít Špinka napsal(a):
> Hi list,
> have anyone seen something like this?
> We have a Perl+C application connecting to Oracle; it uses DBD::Oracle
> and OCI (although it does not seem to actually use OCI in this case). It
> runs more or less fine on Linux, Windows etc. And if it crashes, it has
> signal handlers installed to create a stack trace, collect various
> diagnostics etc. So far so good.
> However, on Solaris on Sparc, we on some machines get instead just
> short error messsage like "KPEDBG_HDL_POP_FCPTR" and then the program
> dies, without invoking any of the signal handlers. And truss shows it
> actually got some signal that caused it to do this.
> My guess is that this is kpeDbg() function that can be sometimes seen on
> other platforms when the crash is in Oracle libraries - it prints a
> neatly formatted call stack.
> So the question is - have you ever seen something like this? Do you know
> of any way how to get at least some information as to nature of the
> issue? E.g. let the signal get to the Perl+C program or get the call stack.
> Version info: Instant Client, database:, 11.2.?
> Tried: adding bequeath_detach=yes and DIAG_SIGHANDLER_ENABLED=FALSE to
> sqlnet.ora, but to no avail.
> Vit
> --

Received on Mon Jan 14 2013 - 23:44:32 CET

Original text of this message