fb_lock_mgr crashed with SIGSEGV in __libc_start_main()

[Pavel Mlčoch]

crash when I close application economy10

ProblemType: Crash
Architecture: i386
Date: Fri Mar 21 16:05:21 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/firebird/2.0/bin/fb_lock_mgr
Package: firebird2.0-classic 2.0.3.12981.ds1-5ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/firebird/2.0/bin/fb_lock_mgr
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: firebird2.0
Stacktrace:
 #0 0x0804dabc in ?? ()
 #1 0x0804b0dd in ?? ()
 #2 0xb7d77450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #3 0x0804afd1 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Title: fb_lock_mgr crashed with SIGSEGV in __libc_start_main()
Uname: Linux 2.6.24-12-generic i686
UserGroups: mythtv
SegvAnalysis:
 Segfault happened at: 0x804dabc <geteuid@plt+11044>: movzwl 0x2(%edi),%eax
 PC (0x0804dabc) ok
 source "0x2(%edi)" (0x00002d46) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA

[Apport retracing service (apport)]

StacktraceTop:main (argc=<value optimized out>, argv=) at ../src/lock/manager.cpp:74
__libc_start_main () from /lib/tls/i686/cmov/libc.so.6
_start ()

[Alex Peshkoff (peshkoff-mail)]

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.

[Damyan Ivanov (dmn-debian)]

-=| 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 address hidden>

[Popa Adrian Marius (mapopa)]

Please upgrade to Firebird 2.5 and ubuntu 12.04

Firebird 2.0 is EOL
http://www.firebirdnews.org/?p=7376

Firebird 2.5 is also in 8.04 PPA

http://www.firebirdnews.org/?p=7981

[Alex Peshkoff (peshkoff-mail)]

On 11/16/12 11:38, Popa Adrian Marius wrote:
> Please upgrade to Firebird 2.5 and ubuntu 12.04

BTW - looks like this is bad Damyan's patch to close fb_lock_mgr process
in the end of build.
Probably vanilla 2.0.7 will be enough for them - not sure that with
2.6.24 (and that time libc) 2.5 os very good choice.
....

>
> Firebird 2.0 is EOL
> http://www.firebirdnews.org/?p=7376
>
>
> Firebird 2.5 is also in 8.04 PPA
>
> http://www.firebirdnews.org/?p=7981
>
> ** Changed in: firebird2.0 (Ubuntu)
> Status: New => Fix Released
>

[Popa Adrian Marius (mapopa)]

Let's hope they migrated to the next LTS :)

Migration path is 2.0.7 Vanilla or Firebird 2.1 (Debian and Ubuntu doesn't package 2.0 it anymore)

So if they want 2.5 the safe path is SuperServer

IMPORTANT: Note affecting all Firebird 2.5.x Linux builds
The recommended Linux kernel version is 2.6.34 and glibc should be version 2.12 or higher. Minimum - kernel 2.6.27 and glibc 2.7.
If your glibc version is lower than v.2.7, it must be upgraded before using Firebird 2.5 Classic/Superсlassic.

Here is the disscussion around the issue
http://tech.dir.groups.yahoo.com/group/firebird-support/message/113059