NSJavaSetupVirtualMachine() and signal() call order
NSJavaSetupVirtualMachine() and signal() call order
- Subject: NSJavaSetupVirtualMachine() and signal() call order
- From: Jesse Grosjean <email@hidden>
- Date: Wed, 26 Jan 2005 16:16:46 -0500
Does anyone know why registering for a signal before loading the JVM
causes an application to crash when run under MallocDebug or
GuardMalloc. Here's my code that causes the crash:
signal(SIGILL, HBCrashHandler_Signal);
NSJavaSetupVirtualMachine();
But if I switch the order of those lines everything seems to work fine.
Also could this be leading to other problems when the app is not being
run under MallocDebug. Thanks for any help.
Here are the crash and console logs that show up when the above code is
run under MallocDebug.
From the console log:
[Session started at 2005-01-26 15:49:54 -0500.]
Java HotSpot(TM) Client VM warning: Attempt to guard stack yellow zone
failed.
Java HotSpot(TM) Client VM warning: Attempt to guard stack red zone
failed.
dyld:
/Users/jessegrosjean/working/builds/TestJava.app/Contents/MacOS/
TestJava multiple definitions of symbol _zlibVersion
/usr/lib/libz.1.dylib(zutil.o) definition of _zlibVersion
/System/Library/Frameworks/JavaVM.framework/Versions/1.3.1/Libraries/
libzip.jnilib(zip.o) definition of _zlibVersion
From the crash log:
Link (dyld) error:
dyld:
/Users/jessegrosjean/working/builds/TestJava.app/Contents/MacOS/
TestJava multiple definitions of symbol _zlibVersion
/usr/lib/libz.1.dylib(zutil.o) definition of _zlibVersion
/System/Library/Frameworks/JavaVM.framework/Versions/1.3.1/Libraries/
libzip.jnilib(zip.o) definition of _zlibVersion
Thanks,
Jesse
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden