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

Thanks for reporting this issue.

On 04/11/2010 14:49, Weeber, Burkhard wrote:
> I updated my Cygwin with the latest available from the "setup.exe".

Do you know which version of Xserver that worked you updated from?

Examining /var/log/setup.log and/or using setup to revert to the previous
version should tell you.

> Now XWin.exe gets a Signal 11 (Segmentation violation) when a font switch (-fn) is on the command line.
> Command:
> $ ssh -Y myaix "aixterm -fullcursor -geometry 81x30-125+93 -e /usr/local/bin/"
> Is OK.
> $ ssh -Y myaix "aixterm -fullcursor -geometry 81x30-125+93 -fn 6x10 -e /usr/local/bin/"
> Fails.
> I have a font server running on AIX6.1 and before the start this font server is added by xset command.
> This worked well until the update.
> Also the xlsfonts command of cygwin distribution causes XWin to SIGSEGV.
> Also when specifying "-fp tcp/myfontserver:7100" on the XWin start line any X-Program will cause a SIGSEGV.

I'm afraid I'm not able to reproduce this (testing using an xfs running on
Solaris, I don't have access to AIX).

Can you please obtain a backtrace as follows:
1) Install gdb (for gdb) and sysvinit (for pidof) packages
2) Start XWin using your normal method
3) In a non-X terminal window, run gdb --pid=`pidof /usr/bin/XWin`
4) Type 'c' at the '(gdb)' prompt
5) Reproduce your crash
6) Type 'bt full' at the '(gdb)' prompt.

Volunteer Cygwin/X X Server maintainer

Unsubscribe info:
Problem reports:

  reply	other threads:[~2010-11-05 19:52 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 [this message]
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

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