http://bugs.freedesktop.org/show_bug.cgi?id=13979
Matthias Hopf changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mhopf@suse.de
--- Comment #8 from Matthias Hopf 2008-01-18 04:46:15 PST ---
For the future: it helps a lot if the driver is compiled with "-O0 -g3" instead
of "-O2 -g" (the default). 'make CFLAGS="-O0 -g3" does the trick
(alternatively, './configure CFLAGS="-O0 -g3"' and just make afterwards). In
this case it wouldn't help, because you're crashing deep inside RandR.
Yes, core files can be such large. Especially with the Xserver, the core file
might contain the whole mapped memory (including graphics memory).
Ok, as you invoked xrandr with --size, some notes:
xrandr --size (or -s) is RandR 1.1 . You shouldn't use it with a RandR 1.2
capable driver. The command to change the resolution is 'xrandr --output
<outname> --mode <modename>'. Please test. That said, all user interface tools
ATM use RandR 1.1 commands.
RandR 1.1 commands shouldn't crash the Xserver (and they don't for me), but it
seems that this is not a bug in the driver, but in the RandR implementation (no
driver function is involved in your backtrace). Can you try a newer Xserver?
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
_______________________________________________
xorg-team mailing list
xorg-team@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-team
--
To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org
For additional commands, e-mail: radeonhd+help@opensuse.org