public inbox for
help / color / mirror / Atom feed
From: "Weeber, Burkhard" <>
To: <>
Subject: AW: Xwin SIGSEGV when font server should be queried
Date: Mon, 08 Nov 2010 10:21:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

The previous version, that was stable for xorg-server was 1.8.2-1,
according to setup.log.

The gdb stack trace is not very talkative:
Loaded symbols for /usr/bin/cygXrender-1.dll
[Switching to thread 8788.0x2740]
(gdb) c
(no debugging symbols found)

Program received signal SIGSEGV, Segmentation fault.
[Switching to thread 8788.0x1178]
0x005508b5 in ?? ()
(gdb) bt full
#0  0x005508b5 in ?? ()
No symbol table info available.
#1  0x0000000c in ?? ()
No symbol table info available.
#2  0x005fa120 in ?? ()
No symbol table info available.
#3  0x00000000 in ?? ()
No symbol table info available.

I will download current source and compile it with -g .

Something funny about it:
I had the "xset fp+ tcp/mystique:7100" commented out in the
Then I started XWin, attached the gdb and issued the xset command from
within a AIX aixterm shell.
Then I started a window that has to use a font server font and it

Then I activated the xset command in the .startxwinrc again and the XWin
crashed again.
I keep on researching.


Geschaeftsfuehrer/Managing Directors: Christoph Hahn-Woernle, Frank Apel
HRB 17335, Amtsgericht Stuttgart (Commercial Register District Court Stuttgart)
St.-Nr. 99064/06051, USt-IdNr./VAT Reg.No.: DE 203036780

Unsubscribe info:
Problem reports:

  reply	other threads:[~2010-11-08 10:21 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   ` Weeber, Burkhard [this message]
2010-11-08 13:48     ` AW: " 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).