public inbox for
help / color / mirror / Atom feed
From: Jon TURNEY <>
Subject: Re: AW: Xwin SIGSEGV when font server should be queried
Date: Wed, 10 Nov 2010 16:12:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 08/11/2010 14:11, Weeber, Burkhard wrote:
> I did a bit of further reseach.
> It looks like it does not have anything to do with the way the font server is queried, 
> but rather the way the startup is done.
> When I have the font server added during the XWin startup - either in the startxwin.bat, or a bash-script I call from there, the XWin SIGSEGVs.
> When I let the XWin come up with a few of my fav screens, and I then add the font server either from a cygwin shell or from a client shell the font server is subsequently queried correctly and the SIGSEGV does not appear.
> Strange.
> Anyway.
> Thanks for the exe to create a full stack trace.
> Here it is:
> (gdb) bt full
> #0  0x005b56a2 in doListFontsWithInfo (client=0x10981dc8, c=0x108693f0)

Thanks for obtaining this backtrace.

With this and the startup script you posted, I have managed to reproduce the

It looks like this has been caused by the changes in Xserver 1.9 to fix a
different bug with xfs [1].  The problem is a use-after-free, so that probably
explains why it sometimes works if you do things in a different order.

I noticed that setup is only offering a choice of 1.9.0-2 or 1.9.2-1, which
isn't a very smart thing to do, so I've rearranged things so now 1.8.2-1
should be offered as the previous version.


Volunteer Cygwin/X X Server maintainer

Unsubscribe info:
Problem reports:

      reply	other threads:[~2010-11-10 16:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 14:49 Weeber, Burkhard
2010-11-05 19:52 ` Jon TURNEY
2010-11-08 10:21   ` AW: " Weeber, Burkhard
2010-11-08 13:48     ` Jon TURNEY
2010-11-09  8:45       ` AW: " Weeber, Burkhard
2010-11-09  9:52       ` Weeber, Burkhard
2010-11-08 14:11   ` Weeber, Burkhard
2010-11-10 16:12     ` Jon TURNEY [this message]

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:

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

  git send-email \ \ \ \ \

* 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).