From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: 25875@debbugs.gnu.org
Subject: bug#25875: 26.0.50; Hang logging out of MS-Windows
Date: Sat, 25 Feb 2017 22:33:20 +0200 [thread overview]
Message-ID: <83lgsuqacv.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58ogpHLJrRzhtZs=Fjr=CFjxmWC-ZhNuZBPtji+Y2iy8hOg@mail.gmail.com> (message from Richard Copley on Sat, 25 Feb 2017 19:35:28 +0000)
> From: Richard Copley <rcopley@gmail.com>
> Date: Sat, 25 Feb 2017 19:35:28 +0000
>
> On MS Windows, Emacs sometimes hangs when shutting down or logging out.
How did you shut it down in this case? This part:
> #2 0x0000000400266caf in sys_sleep (seconds=1000)
> at ../../repo/src/w32.c:3075
> No locals.
> #3 0x0000000400238225 in w32_wnd_proc (hwnd=0x1f076a, msg=22, wParam=1,
> lParam=0) at ../../repo/src/w32fns.c:4805
seems to indicate that you shut down your Windows session or
something?
> (This build includes 5114b3a204..: Eli Zaretskii 2017-02-23 Avoid
> quitting inside a critical section on MS-Windows, see #25279).
>
> I've included backtraces for all the threads having Emacs functions on
> the stack, because I can't tell which are deadlocked, if any. (2 and 3?)
I'm not sure I see any of them deadlocked. Each one is waiting for
something it should.
> Also got these from thread 2, frame 2.
>
> (gdb) print crit
> $1 = (CRITICAL_SECTION *) 0x401bc6a20 <crit_real>
> (gdb) print crit_real
> $2 = {DebugInfo = 0xffffffffffffffff, LockCount = -1, RecursionCount = 0,
> OwningThread = 0x0, LockSemaphore = 0x0, SpinCount = 33556432}
Any reasons why this drew your attention?
> Configured using:
> 'configure --prefix=/mingw64 --with-modules
> --enable-locallisppath=/c/emacs/site-lisp
> CPPFLAGS=-D_WIN32_WINNT=_WIN32_WINNT_WIN7 'CFLAGS=-O0 -g -ggdb''
Why are you setting _WIN32_WINNT to this value when compiling Emacs?
next prev parent reply other threads:[~2017-02-25 20:33 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 19:35 bug#25875: 26.0.50; Hang logging out of MS-Windows Richard Copley
2017-02-25 19:41 ` Richard Copley
2017-02-25 20:36 ` Eli Zaretskii
2017-02-25 21:13 ` Richard Copley
2017-02-26 15:47 ` Eli Zaretskii
2017-02-26 18:26 ` Richard Copley
2017-02-25 20:33 ` Eli Zaretskii [this message]
2017-02-25 21:07 ` Richard Copley
2017-02-25 21:30 ` Richard Copley
2017-02-25 21:37 ` Richard Copley
2017-02-25 22:02 ` Richard Copley
2017-02-26 15:47 ` Eli Zaretskii
2017-02-26 18:37 ` Richard Copley
2017-02-26 15:44 ` Eli Zaretskii
2017-02-26 18:04 ` Ken Brown
2017-02-26 18:25 ` Eli Zaretskii
2017-02-26 18:58 ` Ken Brown
2017-02-26 19:25 ` Eli Zaretskii
2017-02-26 23:38 ` Ken Brown
2017-02-27 8:14 ` Richard Copley
2017-02-27 15:36 ` Eli Zaretskii
2017-02-27 19:04 ` Richard Copley
2017-02-27 19:16 ` Eli Zaretskii
2017-02-27 19:23 ` Richard Copley
2017-02-27 19:30 ` Richard Copley
2017-02-27 19:39 ` Ken Brown
2017-02-27 19:46 ` Richard Copley
2017-02-27 19:56 ` Richard Copley
2017-02-27 20:19 ` Ken Brown
2017-02-27 20:27 ` Eli Zaretskii
2017-02-27 20:52 ` Richard Copley
2017-02-27 20:58 ` Eli Zaretskii
2017-02-27 21:09 ` Richard Copley
2017-02-28 3:30 ` Eli Zaretskii
2017-02-28 6:37 ` Richard Copley
2017-02-27 22:37 ` Ken Brown
2017-02-27 23:03 ` Richard Copley
2017-02-28 3:35 ` Eli Zaretskii
2017-02-28 7:21 ` Richard Copley
2017-02-28 15:36 ` Eli Zaretskii
2017-02-28 16:40 ` Ken Brown
2017-02-28 16:44 ` Eli Zaretskii
2017-02-28 18:59 ` Richard Copley
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=83lgsuqacv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25875@debbugs.gnu.org \
--cc=rcopley@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.