public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu> To: cygx <cygwin-xfree@cygwin.com> Cc: xorg@pdx.freedesktop.org Subject: Crashing after two or three server resets Date: Sun, 11 Jan 2004 03:12:00 -0000 [thread overview] Message-ID: <4000BF0E.2090102@msu.edu> (raw) Upon looking into this problem, I have found the following: 1) The crashes after a few resets in XFree86-xserv-4.3.0-35 are due to double-freeing of timers in the xc/programs/Xserver/os/ code. A fix for this was added to the XFree86 tree back in October, shortly after the changes to WaitForSomething that changed the order of timeout processing and input event processing. This fix is already in our xorg tree, so... 2) I tried the server from xorg and it crashes in a different place: Program received signal SIGSEGV, Segmentation fault. 0x61093af5 in strtosigno () from /usr/bin/cygwin1.dll (gdb) bt #0 0x61093af5 in strtosigno () from /usr/bin/cygwin1.dll #1 0x6103eb65 in free () from /usr/bin/cygwin1.dll #2 0x006f6038 in FontFileFreeEntry () #3 0x006f6075 in FontFileFreeTable () #4 0x006f6222 in FontFileFreeDir () #5 0x006ec6cf in FontFileFreeFPE () #6 0x00412096 in FreeFPE () #7 0x00414548 in FreeFontPath () #8 0x00414e2d in FreeFonts () #9 0x0040187d in main () (gdb) So, it seems that there is still a double-free problem in dix/fonts.c. Ugh... this ought to be fun to fix :) I might look into this more, but I can't promise anything (particularly since no Cygwin/X users are complaining about crashes on resets). Harold
next reply other threads:[~2004-01-11 3:12 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-11 3:12 Harold L Hunt II [this message] 2004-01-11 14:29 ` Takuma Murakami 2004-01-11 17:17 ` Alexander Gottwald 2004-01-11 17:27 ` Thomas Dickey 2004-01-11 18:00 ` Alexander Gottwald 2004-01-11 17:50 ` Alexander Gottwald 2004-01-11 20:21 ` Harold L Hunt II 2004-01-12 0:00 ` Alexander Gottwald
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=4000BF0E.2090102@msu.edu \ --to=huntharo@msu.edu \ --cc=cygwin-xfree@cygwin.com \ --cc=xorg@pdx.freedesktop.org \ /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: linkBe 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).