site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On 21 nov 2005, at 15:43, Jonas Maebe wrote: Found the solution! Change into sa.sa_flags = SA_SIGINFO|SA_64REGSET; Now the program I posted works fine when compiled for 64bit. Jonas PS: is it expected that "otool -L" fails on 64 bit programs? I get $ file sig4 sig4: Mach-O 64-bit executable ppc64 $ otool -L sig4 sig4: is not an object file _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... I've now tried a 64bit version and sure enough, that one always crashes with a SIGBUS when returning from the signal handler, even if the handler doesn't do anything. Warrants a radar, I'd say. I've put the adjusted 64bit version of the test program below (which, as I said, crashes even if you remove all code from "signal_handler"): sa.sa_flags = SA_SIGINFO; The comments in /usr/include/sys/signal.h say SA_64REGSET is only necessary to get access to the 64bit registers when you're in 32bit mode, but apparently it's also required for 64bit mode (or do you have to use another option besides -m64 to get a "proper" 64bit program?) This email sent to site_archiver@lists.apple.com