🚀 go-pugleaf

Exception handling is crucial to our application, but I have a 
problem when using try/catch in Kylix-built C++ shared objects. 
If an exception occurs, execution enters the catch block, but 
then the program seg faults and terminates immediately. If there 
is a function call in the catch block, the seg fault occurs 
during the function call set-up. If there are no function calls, 
the seg fault occurs in the stack clean-up at the end of the 
catch block. Stepping through the assembly code, it appears that the bpx register gets messed up in libborcrtl.so.

Has anyone found a fix or workaround for this problem? It only 
occurs in shared objects.

The following simple program works correctly using g++, but fails using Kylix.

Thanks very much to anyone who can help, even if it's just to 
say "there is no fix".
- Dave Devlin

*** Here's my main program: ***

#ifdef __BORLANDC__
extern "C" __declspec(dllexport) void SharedObjFunc();
#else
extern "C" void SharedObjFunc();
#endif

int main(void)
{
	SharedObjFunc();
	return 0;
}

*** Here's my shared object: ***

#include <stdio.h>

#ifdef __BORLANDC__
extern "C" __declspec(dllexport) void SharedObjFunc()
#define EXPORT_FUNC   
#else
extern "C" void SharedObjFunc()
#endif
{
	try
	{
		printf("Throwing...\n");
		throw 1;
	}
	catch(...)
	{
		printf("...in catch. Kylix does not get here\n");
	}
	printf("...after catch. Kylix does not get here.\n");
}