Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#10781 - catalyst driver segfault due to DRILockWinInfo()
Attached to Project:
Arch Linux
Opened by Pierre (baude) - Monday, 30 June 2008, 05:22 GMT
Last edited by Greg (dolby) - Monday, 07 July 2008, 19:34 GMT
Opened by Pierre (baude) - Monday, 30 June 2008, 05:22 GMT
Last edited by Greg (dolby) - Monday, 07 July 2008, 19:34 GMT
|
DetailsDescription:
When using a 3D program I wrote on my machine, I get a segfault on exit. This does NOT occur on another machine with a different hardware. I so ran my program with gdb and I get this on exit : Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb67036d0 (LWP 5401)] 0xb60a9e28 in DRILockWinInfo () from /usr/lib/xorg/modules/dri//fglrx_dri.so Additional info: * package version(s) catalyst 8.6-1 |
This task depends upon
Comment by Jan de Groot (JGC) -
Monday, 30 June 2008, 07:37 GMT
Please submit a bugreport upstream. This is a binary-only driver that we can't bugfix.
Comment by Pierre (baude) -
Tuesday, 01 July 2008, 02:37 GMT
Ok, sorry. I mainly wanted to signal it.