public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "Weeber, Burkhard" <b.weeber@viastore.com>
To: <cygwin-xfree@cygwin.com>
Subject: AW: 1.9.2.0: Xwin SIGSEGV when font server should be queried
Date: Mon, 08 Nov 2010 14:11:00 -0000	[thread overview]
Message-ID: <578A937A9A719E4CB564C5A9013A6012032EA7B0@MAILD.viastore.de> (raw)
In-Reply-To: <4CD46065.4080501@dronecode.org.uk>

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)
    at dixfonts.c:920
        fpe = (FontPathElementPtr) 0x109816a0
        err = 85
        name = 0x5b3f36 "\203E▒\001▒h▒e"
        namelen = 2280120
        numFonts = 1628938183
        fontInfo = {firstCol = 51800, lastCol = 34, firstRow = 1,
  lastRow = 0, defaultCh = 1, noOverlap = 0, terminalFont = 0,
  constantMetrics = 0, constantWidth = 0, inkInside = 0, inkMetrics = 0,
  allExist = 0, drawDirection = 0, cachable = 0, anamorphic = 0,
  maxOverlap = 0, pad = 0, maxbounds = {leftSideBearing = 0,
    rightSideBearing = 0, characterWidth = 0, ascent = 0, descent = 5840,
    attributes = 4248}, minbounds = {leftSideBearing = 16384,
    rightSideBearing = 0, characterWidth = 0, ascent = 0, descent = 100,
    attributes = 0}, ink_maxbounds = {leftSideBearing = -24633,
    rightSideBearing = 24855, characterWidth = 12266, ascent = 4168,
    descent = -29488, attributes = 65}, ink_minbounds = {
    leftSideBearing = -13640, rightSideBearing = 34, characterWidth = -29439,
    ascent = 65, descent = -13668, attributes = 34}, fontAscent = 0,
  fontDescent = 0, nprops = 0, props = 0x0,
  isStringProp = 0x1 <Address 0x1 out of bounds>}
        pFontInfo = (FontInfoRec *) 0x1097d4d8
        reply = (xListFontsWithInfoReply *) 0x0
---Type <return> to continue, or q <return> to quit---
        length = 0
        pFP = (xFontProp *) 0x1
        i = 278402720
        aliascount = 0
        finalReply = {type = 0 '\0', nameLength = 0 '\0', sequenceNumber = 0,
  length = 0, minBounds = {leftSideBearing = 0, rightSideBearing = 0,
    characterWidth = -10208, ascent = 4207, descent = 24928,
    attributes = 102}, walign1 = 0, maxBounds = {leftSideBearing = -16392,
    rightSideBearing = 24843, characterWidth = 0, ascent = 0, descent = 0,
    attributes = 0}, walign2 = 0, minCharOrByte2 = 0, maxCharOrByte2 = 0,
  defaultChar = 0, nFontProps = 0, drawDirection = 0 '\0', minByte1 = 0 '\0',
  maxByte1 = 0 '\0', allCharsExist = 0 '\0', fontAscent = 0, fontDescent = 0,
  nReplies = 0}
#1  0x00579a0f in ProcessWorkQueue () at dixutils.c:527
        q = (WorkQueuePtr) 0x108698a8
        p = (WorkQueuePtr *) 0x665de4
#2  0x005eb4f5 in WaitForSomething (pClientsReady=0x106d0ff8) at WaitFor.c:169
        i = 1
        waittime = {tv_sec = 30, tv_usec = 0}
        wt = (struct timeval *) 0x22cba0
        timeout = 570906
        clientsReadable = {fds_bits = {0, 0, 0, 0, 0, 0, 0, 0}}
        clientsWritable = {fds_bits = {277256200, 277256384, 0, 2280408,
    6197569, 278385880, 2280328, 1}}
---Type <return> to continue, or q <return> to quit---
        curclient = 292
        selecterr = 0
        nready = 0
        devicesReadable = {fds_bits = {0, 0, 0, 0, 0, 0, 0, 0}}
        now = 447551595
        someReady = 0
#3  0x0057093e in Dispatch () at dispatch.c:369
        clientReady = (int *) 0x106d0ff8
        result = 0
        client = (ClientPtr) 0x10981dc8
        nready = -1
        icheck = (HWEventQueuePtr *) 0x665aa0
        start_tick = 0
#4  0x0056af00 in main (argc=8, argv=0x10482fa8, envp=0x104480e0)
    at main.c:298
        i = 1
        alwaysCheckForInput = {0, 1}
(gdb)

Thanks for your help

Burkhard
_________________________________________________________________________________________
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:      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/


  parent reply	other threads:[~2010-11-08 14:11 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 [this message]
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:
  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=578A937A9A719E4CB564C5A9013A6012032EA7B0@MAILD.viastore.de \
    --to=b.weeber@viastore.com \
    --cc=cygwin-xfree@cygwin.com \
    /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).