Summary: | Xprt crashes on amd64 (x86-64) | ||||||
---|---|---|---|---|---|---|---|
Product: | xprint | Reporter: | Drew Parsons <dparsons> | ||||
Component: | Server: Other | Assignee: | Roland Mainz <roland.mainz> | ||||
Status: | RESOLVED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | high | CC: | anders, ukh | ||||
Version: | unspecified | ||||||
Hardware: | x86 (IA32) | ||||||
OS: | Linux (All) | ||||||
URL: | http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=278510 | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Drew Parsons
2004-11-24 15:41:11 UTC
Created attachment 1371 [details] [review] Xalloc declarations wrong This fast fix allows us to get slightly longer, but Xprt now crashes at another stage - any ideas? I'm running in a gcc 3.4 environment, btw. Program received signal SIGSEGV, Segmentation fault. 0x0000000000407b79 in LookupClient (rid=5161623, client=0x7fbffff6f0) at dixutils.c:316 316 return clients[clientIndex]; (gdb) bt #0 0x0000000000407b79 in LookupClient (rid=5161623, client=0x7fbffff6f0) at dixutils.c:316 #1 0x0000000000407e9a in BlockHandler (pTimeout=0x7fbffff578, pReadmask=0xb50dc0) at dixutils.c:431 #2 0x0000000000444d87 in WaitForSomething (pClientsReady=0x7fbffff5b0) at WaitFor.c:304 #3 0x0000000000430f0a in Dispatch () at dispatch.c:253 #4 0x000000000041379f in main (argc=10, argv=0x7fbffffb18) at main.c:364 Please ignore my "Xalloc" patch - it looks like the segfault occurs at different places, depending on the compiler used. (I'm using gcc-3.4.3.) The new experimental debian-version, 0.1.0.alpha1-1, works under amd64 with mozilla 1.7.3 , so the amd64-problem seems to be fixed in the 010+ cvs-tree! (In reply to comment #3) > The new experimental debian-version, 0.1.0.alpha1-1, works under > amd64 with mozilla 1.7.3 , so the amd64-problem seems to be fixed in > the 010+ cvs-tree! I got the same confirmation from Suse/AMD64 so I am marking this issue as FIXED. |
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.