humble question about FileMaker breakage
Hello,
perhaps this list is the right place to ask whether filing a bug report
against libc6 would be appropriate or rather not - I do not want to
stupidly busy maintainers with something I have almost no idea about, so
perhaps I may ask for guidance here:
I am running a debianized FileMaker 5.5 Server package that originally
was a RPM package meant to run under RedHat 6.2 or 7.0. It has been
working under Woody and even under the testing version of libc6 it ran fine.
The libc6 upgrade to unstable makes fmserverd segfault.
strace gives me
--- snip ---
open("/lib/libm.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\2605\0"...,
1024) = 1024
fstat64(3, {st_mode=S_IFREG|0644, st_size=130964, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0x40023000
old_mmap(NULL, 133536, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40024000
mprotect(0x40044000, 2464, PROT_NONE) = 0
old_mmap(0x40044000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED,
3, 0x1f000) = 0x40044000
close(3) = 0
open("/lib/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0]Z\1\000"...,
1024) = 1024
fstat64(3, {st_mode=S_IFREG|0755, st_size=1102920, ...}) = 0
old_mmap(NULL, 1113188, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40045000
mprotect(0x4014d000, 31844, PROT_NONE) = 0
old_mmap(0x4014d000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED,
3, 0x107000) = 0x4014d000
old_mmap(0x40153000, 7268, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40153000
close(3) = 0
munmap(0x40012000, 56602) = 0
getpid() = 11175
getrlimit(RLIMIT_STACK, {rlim_cur=2147483647, rlim_max=2147483647}) = 0
setrlimit(RLIMIT_STACK, {rlim_cur=2040*1024, rlim_max=2147483647}) = 0
uname({sys="Linux", node="mybox", ...}) = 0
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
Telling the FileMaker people will probably be useless, so, is this
something I will have to live with, keeping my database on an
installation that will be mummified in a couple years or is this a
flavor of SID and I could report a bug with some hope that it may be
fixed although the breakage is with a closed source program?
Regards,
Andreas von Heydwolff
Vienna, Austria
Reply to: