On Wed, Aug 17, 2005 at 11:59:40AM +0200, Laurent Fousse wrote: > Rebuilding with debugging enabled gives me :
> Program received signal SIGSEGV, Segmentation fault. > 0x0fb07788 in semctl () from /lib/libc.so.6 > (gdb) bt > #0 0x0fb07788 in semctl () from /lib/libc.so.6 > #1 0x1000454c in open_sem (sem_key=1263124) at sf.c:423 > #2 0x100041dc in create_shared_image (base=1263104, image=0x1002a854, > size=265984, shmid=0x1002a858, semid=0x1002a85c) at sf.c:343 > #3 0x10003bb4 in main (argc=1, argv=0x7fd4d9e4) at sf.c:192 > * Steve Langasek [2005-08-16]: > > > I see you have mixed versions of X. You have mostly X.org libraries > > > (6.8.2.dfsg.1-4) but some old XFree86 libraries (libx11-6 > > > 4.3.0.dfsg.1-14). I don't know if you can easily downgrade or upgrade > > > at this point, but you might be experiencing problems in this and other > > > X apps until the transition to X.org settles down in the archive. > > There is no known reason why this should be the case; all X.org libs should > > be binary compatible with (indeed, nearly indentical to) the XFree libs. So > > if this fixes it, the bug very much needs to be assigned to X.org. > From the backtrace, I would rather guess it's libc-related. Actually, I would guess it's kernel-related. Per your original report, you are running: > Kernel: Linux 2.6.12.4-bar This looks like a self-compiled kernel. Please check whether this bug occurs with the Debian kernel packages, or at least check that you have the core CONFIG_SYSVIPC option enabled in your kernel config. If neither enabling CONFIG_SYSVIPC in your custom kernel, nor booting a Debian kernel, fixes this problem for you, *then* we should look at it as a libc problem. :) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
