SIGSEGV in xorg-188.8.131.52 during -resize operation
Thu Sep 23 13:47:00 GMT 2010
On 23/09/2010 14:29, Eliot Moss wrote:
> On 9/23/2010 9:10 AM, Jon TURNEY wrote:
>> On 21/09/2010 23:06, Eliot Moss wrote:
> [I reported crash on resume after Suspend or Hibernate.]
>> Does the crash also occur if you don't use -resize?
>>> Is there a simple procedure for winding back?
>> If you've installed my snapshot as XWin.exe, the easiest way to get the
>> 1.8.2-1 version back is to
>> reinstall it using setup.
> Right; sorry I wasn't clear. I was trying the snapshot because
> 1.8.2-1 fails in the same way. What I meant was: Can I easily
> go back to a consistent set of X.org files some time *before*
> that ..
I see, thanks for the clarification.
You should use setup to revert to Xserver 1.8.0-1, then :-)
>> Unfortunately, I can't reproduce this on my Win7 system, although it is
>> quite possible that this is specific to the display driver or hardware.
> I have a Toshiba Portege M750. It has Intel Display drivers.
> But you know what, that got me thinking: I believe those
> drivers were updated recently and maybe I should try winding
> *them* back.
>> If you can use gdb to generate a backtrace for this segfault, that would be
>> most helpful.
> I understand gdb generally and all. Can you give a bit of guidance about how
> to start things (edits to startxwn.bat?) with gdb, to get you that back trace?
You may find it easiest and most reliable to start XWin normally, and then (in
a separate terminal window), use ps to identify the XWin processes PID, then
use gdb --pid=<pid> to attach to the running XWin process, 'c' at the (gdb)
prompt and then reproduce your crash...
Volunteer Cygwin/X X Server maintainer
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin-xfree