public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: moss@cs.umass.edu
Subject: Re: SIGSEGV in xorg-1.8.2.0 during -resize operation
Date: Thu, 23 Sep 2010 13:47:00 -0000	[thread overview]
Message-ID: <4C9B5A6A.6020901@dronecode.org.uk> (raw)
In-Reply-To: <4C9B563D.9060607@cs.umass.edu>

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?
>
> Yes.
>
>>> 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...

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2010-09-23 13:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 22:06 Eliot Moss
2010-09-23 13:10 ` Jon TURNEY
2010-09-23 13:29   ` Eliot Moss
2010-09-23 13:47     ` Jon TURNEY [this message]
2010-09-23 13:56       ` Eliot Moss
2010-09-23 14:55       ` Eliot Moss
2010-09-23 15:56         ` Jon TURNEY
2010-09-23 19:35           ` Eliot Moss
2010-09-27 14:54             ` Jon TURNEY
2010-09-27 15:05               ` Eliot Moss
2010-09-27 20:52               ` Eliot Moss
2010-09-27 21:04               ` Eliot Moss
2010-09-23 22:08           ` Eliot Moss
  -- strict thread matches above, loose matches on Subject: below --
2010-08-09 21:15 Ryan Johnson
2010-08-09 22:02 ` Jon TURNEY
2010-08-10  5:48   ` Ryan Johnson
2010-08-12 15:46     ` Jon TURNEY
2010-08-12 16:04       ` Ryan Johnson
2010-08-12 17:51         ` Jon TURNEY
2010-08-31 17:06           ` Jon TURNEY
2010-09-01 10:15             ` Ryan Johnson
2010-09-01 17:55               ` Jon TURNEY
2010-09-03 23:10             ` Ryan Johnson
2010-09-07 13:51               ` Jon TURNEY
2010-09-06 21:01             ` Ryan Johnson
2010-09-06 21:38               ` Ryan Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C9B5A6A.6020901@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@cygwin.com \
    --cc=moss@cs.umass.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).