public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-xfree <cygwin-xfree@cygwin.com>
Subject: Re: X server crash when running texworks
Date: Sat, 31 Mar 2012 15:27:00 -0000	[thread overview]
Message-ID: <4F77221E.2010204@cornell.edu> (raw)
In-Reply-To: <4F76DC6B.6070704@dronecode.org.uk>

On 3/31/2012 6:28 AM, Jon TURNEY wrote:
> On 30/03/2012 12:36, Jon TURNEY wrote:
>> On 29/03/2012 20:59, Ken Brown wrote:
>>> On 3/29/2012 8:14 AM, Jon TURNEY wrote:
>>>>
>>>> Not so good :-(.  Thanks for testing it, anyway.
>>>>
>>>> I found a rather bad crash bug I'd introduced and fixed that, so you might
>>>> want to try today's snapshot [1], but I'm not confident that I fixed the
>>>> problem you saw, so a backtrace would be helpful if you still get crashes.
>>>
>>> OK, I'm running it now and have attached gdb to it.  The good news is that
>>> I've been running it for a couple hours with no crash, and I've used texworks
>>> and have opened many tex files and pdf files in it without a problem.  The bad
>>> news is that texworks becomes unresponsive and has to be killed whenever I try
>>> to compile a tex file.  I have no idea whether this is due to an X server
>>> problem or something completely different.  Anyway, I'll post a backtrace if
>>> the server crashes.
>>>
>>> In case you want to try to reproduce the current problem, start texworks, open
>>> a tex file (such as the file test1.tex whose contents I listed at the
>>> beginning of this thread), and click on the icon at the left end of the
>>> toolbar (brown triangle on a green background).  This is supposed to cause
>>> test1.tex to get compiled, but for me it just causes texworks to become
>>> unresponsive.  This was working properly with the previous version of the X
>>> server (until the server crashed).
>>
>> Thanks for testing this X server snapshot.
>>
>> For me, the problem of texworks hanging only occurs very intermittently.  It
>> seems to be blocked deep in QtCore, waiting for the spawned process to
>> terminate (which has already happened).
>
> Attaching to the texworks process, I get a backtrace like this:
>
> (gdb) bt
> #0  0x7c90e514 in ntdll!LdrAccessResource () from
> /cygdrive/c/WINDOWS/system32/ntdll.dll
> #1  0x7c90df4a in ntdll!ZwWaitForMultipleObjects () from
> /cygdrive/c/WINDOWS/system32/ntdll.dll
> #2  0x7c809590 in KERNEL32!CreateFileMappingA () from
> /cygdrive/c/WINDOWS/system32/kernel32.dll
> #3  0x7c80a115 in WaitForMultipleObjects () from
> /cygdrive/c/WINDOWS/system32/kernel32.dll
> #4  0x610ce614 in select_stuff::wait(_types_fd_set*, _types_fd_set*,
> _types_fd_set*, unsigned long) ()
>     from /usr/bin/cygwin1.dll
> #5  0x610cf02b in cygwin_select () from /usr/bin/cygwin1.dll
> #6  0x610d33d5 in _sigfe () from /usr/bin/cygwin1.dll
> #7  0x0022b87c in ?? ()
> #8  0x6d445820 in cygQtCore-4!_ZN15QProcessManager11qt_metacastEPKc () from
> /usr/bin/cygQtCore-4.dll
> #9  0x6d446e97 in cygQtCore-4!_ZN15QProcessPrivate15waitForFinishedEi () from
> /usr/bin/cygQtCore-4.dll
> #10 0x6d40fb85 in cygQtCore-4!_ZN8QProcess15waitForFinishedEi () from
> /usr/bin/cygQtCore-4.dll
> #11 0x6d41286c in cygQtCore-4!_ZN8QProcess7executeERK7QStringRK11QStringList
> () from /usr/bin/cygQtCore-4.dll
> #12 0x0043a350 in ?? ()
> #13 0x0047b8c5 in ?? ()
> #14 0x6d46e733 in cygQtCore-4!_ZN11QMetaObject8activateEP7QObjectPKS_iPPv ()
> from /usr/bin/cygQtCore-4.dll
> #15 0x6bc8b99b in cygQtGui-4!_ZN7QAction9triggeredEb () from
> /usr/bin/cygQtGui-4.dll
> #16 0x6bc8bb9a in cygQtGui-4!_ZN7QAction8activateENS_11ActionEventE () from
> /usr/bin/cygQtGui-4.dll
> #17 0x6c08dd06 in cygQtGui-4!_ZN11QToolButton14nextCheckStateEv () from
> /usr/bin/cygQtGui-4.dll
> #18 0x6bfe0185 in cygQtGui-4!_ZN22QAbstractButtonPrivate5clickEv () from
> /usr/bin/cygQtGui-4.dll
> #19 0x6bfe0426 in
> cygQtGui-4!_ZN15QAbstractButton17mouseReleaseEventEP11QMouseEvent () from
> /usr/bin/cygQtGui-4.dll
> #20 0x6c08ddac in
> cygQtGui-4!_ZN11QToolButton17mouseReleaseEventEP11QMouseEvent () from
> /usr/bin/cygQtGui-4.dll
> #21 0x6bcd8769 in cygQtGui-4!_ZN7QWidget5eventEP6QEvent () from
> /usr/bin/cygQtGui-4.dll
> #22 0x6bc90fec in
> cygQtGui-4!_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent () from
> /usr/bin/cygQtGui-4.dll
> #23 0x6bc95e45 in cygQtGui-4!_ZN12QApplication6notifyEP7QObjectP6QEvent ()
> from /usr/bin/cygQtGui-4.dll
> #24 0x6d45cefd in
> cygQtCore-4!_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent () from
> /usr/bin/cygQtCore-4.dll
> #25 0x6bc91d98 in
> cygQtGui-4!_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb
>      () from /usr/bin/cygQtGui-4.dll
> #26 0x6bd007ed in cygQtGui-4!_ZN9QETWidget19translateMouseEventEPK7_XEvent ()
> from /usr/bin/cygQtGui-4.dll
> #27 0x6bcff421 in cygQtGui-4!_ZN12QApplication15x11ProcessEventEP7_XEvent ()
> from /usr/bin/cygQtGui-4.dll
> #28 0x6bd21f82 in cygQtGui-4!_ZN23QGuiEventDispatcherGlibC2EP7QObject () from
> /usr/bin/cygQtGui-4.dll
> #29 0x5efecb08 in g_main_context_dispatch () from /usr/bin/cygglib-2.0-0.dll
> #30 0x5efed208 in g_main_context_dispatch () from /usr/bin/cygglib-2.0-0.dll
> #31 0x5efed3cf in g_main_context_iteration () from /usr/bin/cygglib-2.0-0.dll
> #32 0x6d480671 in
> cygQtCore-4!_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
> ()
>     from /usr/bin/cygQtCore-4.dll
> #33 0x6bd21cb7 in
> cygQtGui-4!_ZN23QGuiEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
> ()
>     from /usr/bin/cygQtGui-4.dll
> #34 0x6d45c587 in
> cygQtCore-4!_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE ()
>     from /usr/bin/cygQtCore-4.dll
> #35 0x6d45c7f7 in
> cygQtCore-4!_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE () from
> /usr/bin/cygQtCore-4.dll
> #36 0x6d4605d6 in cygQtCore-4!_ZN16QCoreApplication4execEv () from
> /usr/bin/cygQtCore-4.dll
> #37 0x00402bbe in ?? ()
> #38 0x61006d68 in _cygwin_exit_return () from /usr/bin/cygwin1.dll
> #39 0x00000001 in ?? ()
> #40 0x20010100 in ?? ()
> #41 0x00000000 in ?? ()
>
> I'm guessing this is waiting for the pdftex process to terminate, but ps shows
> it as '(defunct)' already...

I wanted to do some further tests, but I thought I should install the 
latest Cygwin snapshot (2012-03-30) first.  With that Cygwin snapshot, 
the XWin snapshot of 20120329 won't start.  It hangs while displaying 
the xterm window.  I attached gdb to it at that point, but when I then 
clicked on the title bar of the xterm window (which was still not fully 
displayed), XWin exited:

(gdb) c
Continuing.
[Inferior 1 (process 3256) exited with code 031777777777]
(gdb) bt full
No stack.

Ken

--
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/


  reply	other threads:[~2012-03-31 15:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24 19:48 Ken Brown
2012-03-26 19:47 ` Ken Brown
2012-03-26 20:07   ` Jon TURNEY
2012-03-26 20:33     ` Ken Brown
2012-03-28 11:16       ` Jon TURNEY
2012-03-28 12:28         ` Ken Brown
2012-03-28 12:46           ` Ken Brown
2012-03-29 12:14             ` Jon TURNEY
2012-03-29 20:00               ` Ken Brown
2012-03-29 20:21                 ` Yaakov (Cygwin/X)
2012-03-29 21:01                   ` Ken Brown
2012-03-30 11:36                 ` Jon TURNEY
2012-03-31 10:29                   ` Jon TURNEY
2012-03-31 15:27                     ` Ken Brown [this message]
2012-04-01  6:07                       ` Jim Reisert AD1C
2012-04-01 13:36                         ` Jon TURNEY
2012-04-02 12:05                       ` Ken Brown
2012-04-02 16:06                         ` Jim Reisert AD1C
2012-04-02 21:14                         ` Ken Brown
2012-04-02 22:50                           ` Yaakov (Cygwin/X)
2012-04-01 13:40                     ` Jon TURNEY
2012-03-28  9:35 ` Yaakov (Cygwin/X)

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=4F77221E.2010204@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).