Tuesday, July 26, 2011
Firebird 2.5 SuperServer and MacOSX 10.7 (Lion)
There is a small problem with Firebird 2.5 SuperServer and MacOSX 10.7 (Lion)...
SuperServer will not start, and produces a crash report header similar to this
Update 26th August 2011
Its not just 2.5 SuperServer, reports have come in that SuperServer for Firebird 2.1.4 will not start, also the same problem exists for Firebird 2.5 SuperClassic.
Process: fbserver 
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: fbguard 
Date/Time: 2011-06-10 07:59:42.374 -0400
OS Version: Mac OS X 10.7 (11A480b)
Report Version: 9
Anonymous UUID: B7EDF790-CE72-4B21-A982-B9EA4F4E2088
Crashed Thread: 1 Dispatch queue: com.apple.libdispatch-manager
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Application Specific Information:
BUG IN CLIENT OF LIBDISPATCH: Do not close random Unix descriptors
The bug is fixed in Firebird 2.5.1 but Firebird 2.5.1 is not available yet. So I have fixed the problem also in the Firebird 2.5 code and produced 32bit and 64bit builds that work properly.
I have had new builds uploaded to Sourceforge to fix the problem with Firebird
2.1.4 SuperServer, you can distinguish the new builds from the old by the build no.
Old = 18393, New = 18393. Because we have some issues with 2.5.1 that are currently being investigated, I plan to update the 2.5 builds on Sourceforge soon.
Update 28th Sep 2011
The Firebird 2.5 builds have also been replaced on Sourceforge, so you just need to download the latest build. However Firebird 2.5 will be replaced by Firebird 2.5.1 very shortly, builds are now taking place and will be QA'd and released shortly.
Any problems - please let me know.
Posted by Paul Beach at 2:04 AM
Subscribe to: Post Comments (Atom)
Thanks Paul, worked a treat.
sorry to bother, but i haven't found other sources for my problem: i'm trying to install firebird 2.5.1 on a fresh osx 10.7 but every installations fail with a "run preinstall script for firebird database" error.
i've tryed every available setup: 32 / 64 bit, CS / SS / lipo, all fail with the same error
A very strange error indeed. Here is what the preinstall script does:
# Script args:
# $0: full path to script
# $1: full path to top level package dir, no trailing slash
# $2: full path to installed location
# $3: ????? Path to install Volume????
# $4: ?????
Perhaps you should take a look at the /var/log/install.log to see if it sheds any light on the problem.
Post a Comment