-=| Alex Peshkoff, Fri, Apr 04, 2008 at 11:47:53AM -0000 |=-
> Lock manager process tries to exit, which should not happen on FB 2.0,
> except when using gds_drop. In theory this may happen due to setting
> lock manager exit flag in shared memory (normally done by gds_drop),
> but to test for it, I need a reproducible test case.
Well, Debian (and Ubuntu) builds Firebird with
-DTERMINALTE_IDLE_LOCK_MANAGER. This may be another cause possible for
fb_lock_mgr to try to exit.
The reason for adding this -D define is that without it, a stale lock
manager is left running on the build machines forever[0].
[0 http://bugs.debian.org/341851 (1.5)
http://bugs.debian.org/416047 (2.0)
(In case you didn't know, the package maintainer only uploads a package
for single architecture. The packages for the rest of supported
architectures are built automatically. The software that does the build
is called a "Build Daemon" or "buildd")
For reference, the patch enabling TERINATE_IDLE_LOCK_MANAGER is at [1]
[1] http://git.debian.org/?p=pkg-
firebird/2.0.git;a=blob;f=debian/patches/terminate-lock-
manager.patch;hb=HEAD
--
dam JabberID: [EMAIL PROTECTED]
** Attachment added: "unnamed"
http://launchpadlibrarian.net/13131555/unnamed
--
fb_lock_mgr crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/204676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
