Bug 3043

Summary: Xvfb segfault on server regeneration or exit
Product: xorg Reporter: Adam Jackson <ajax>
Component: Server/DDX/XvfbAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high CC: roland.mainz
Version: git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Adam Jackson 2005-04-15 16:32:21 UTC 
(gdb) run -ac -screen 0 640x480x24 :2

Starting program: /xorg/imagine/programs/Xserver/Xvfb -ac -screen 0 640x480x24 :2
Could not init font path element /opt/xorg-imagine/lib/X11/fonts/CID/, removing
from list!
Could not init font path element /opt/xorg-imagine/lib/X11/fonts/75dpi/,
removing from list!
Could not init font path element /opt/xorg-imagine/lib/X11/fonts/100dpi/,
removing from list!

Program received signal SIGSEGV, Segmentation fault.
0x08079c36 in FreeGC (value=0x83c9528, gid=0) at gc.c:894
894         (* pGC->funcs->DestroyClip)(pGC);
(gdb) bt
#0  0x08079c36 in FreeGC (value=0x83c9528, gid=0) at gc.c:894
#1  0x08079ddb in FreeGCperDepth (screenNum=65535) at gc.c:995
#2  0x08058088 in main (argc=6, argv=0xbfffefc4, envp=0xffff) at main.c:462
(gdb) print pGC
$1 = 0x83c9528
(gdb) print pGC->funcs
$2 = (GCFuncs *) 0xffff
(gdb) print pGC->funcs->DestroyClip
Cannot access memory at address 0x10013
Comment 1 Roland Mainz 2005-04-16 18:23:14 UTC 
ajax: Somehow the crash sounds familar but I can't remember where I have seen
this before... is it possible that this is a DUPlicate ?
Comment 2 Adam Jackson 2005-04-17 17:16:06 UTC 
if it's a duplicate, then the original needs to be reopened, because this
happens with HEAD (checked out about 90 minutes ago, freshly built).
Comment 3 Adam Jackson 2005-08-01 09:22:38 UTC 
stuart anderson closed a different bug (setting Xvfb back to 8bpp default and
disabling 12 and 30 bit visuals) and now this no longer happens.  i should mark
this a dupe but i can't find the bug number offhand.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.