From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: 17753@debbugs.gnu.org, markus.hoenicka@mhoenicka.de
Subject: bug#17753: Cygwin emacs-X11 core dump
Date: Wed, 17 Sep 2014 20:06:07 +0300 [thread overview]
Message-ID: <83fvfq2n40.fsf@gnu.org> (raw)
In-Reply-To: <5419A604.8060201@cornell.edu>
> Date: Wed, 17 Sep 2014 11:17:24 -0400
> From: Ken Brown <kbrown@cornell.edu>
> CC: 17753@debbugs.gnu.org
>
> On 9/17/2014 6:16 AM, Eli Zaretskii wrote:
> > Anyway, one thing that strikes me (and is consistent across all your
> > reports until now) is that atimer.c functions are run from a separate
> > thread, not the main thread (which is Thread 1). Ken, is this normal
> > in the Cygwin-w32 build?
>
> Timer functions in general are run in the main thread.
That's what I'd expect.
> I don't think the backtrace of Thread 2 can be trusted.
But if you look at all the backtraces posted in this bug, they all
tell the same story: thread 2 seems to run run_timers. So before we
decide this is bogus data, I think we should explore the possibility
that GDB really tells the truth here.
> You can see the expected timer functions running in the main thread, but
> I have no idea what's going on in Thread 2. Is run_timers really being
> called there, or is that just an artifact of a corrupt stack?
Hard to say. But note that do_pending_atimers calls block_atimers
before it calls run_timers, and block_atimers calls pthread_sigmask.
Could this do something weird to the threads, like switch to another
thread?
> I think I should take this to the Cygwin list, unless you have other
> suggestions of things to look at.
Discussing this on the Cygwin list is probably the best place.
Thanks.
next prev parent reply other threads:[~2014-09-17 17:06 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 21:55 bug#17753: Cygwin emacs-X11 core dump markus.hoenicka
2014-06-11 2:51 ` Eli Zaretskii
2014-06-11 6:16 ` Markus Hoenicka
2014-06-11 14:47 ` Eli Zaretskii
2014-06-13 22:53 ` markus.hoenicka
2014-06-11 12:28 ` Ken Brown
2014-06-11 15:03 ` Eli Zaretskii
2014-07-04 21:21 ` markus.hoenicka
2014-07-05 14:03 ` Ken Brown
2014-07-07 21:31 ` markus.hoenicka
2014-07-09 13:57 ` Ken Brown
2014-07-09 14:30 ` Markus Hoenicka
2014-09-17 9:45 ` Markus Hoenicka
2014-09-17 10:16 ` Eli Zaretskii
2014-09-17 10:52 ` Eli Zaretskii
2014-09-17 11:04 ` Markus Hoenicka
2014-09-17 15:17 ` Ken Brown
2014-09-17 17:06 ` Eli Zaretskii [this message]
2014-09-22 7:14 ` Markus Hoenicka
2014-09-22 13:32 ` Ken Brown
2014-09-22 14:04 ` Markus Hoenicka
2014-09-22 14:48 ` Eli Zaretskii
2014-10-07 7:02 ` Markus Hoenicka
2014-10-07 14:56 ` Ken Brown
2014-10-07 15:05 ` Eli Zaretskii
2014-10-07 16:05 ` Markus Hoenicka
2014-10-07 17:04 ` Eli Zaretskii
2014-10-07 20:48 ` Markus Hoenicka
2014-10-09 8:17 ` Markus Hoenicka
2014-10-09 8:56 ` Eli Zaretskii
2014-10-09 9:08 ` Markus Hoenicka
2014-10-09 10:35 ` Eli Zaretskii
2014-10-09 10:44 ` Markus Hoenicka
2014-10-09 11:22 ` Eli Zaretskii
2014-10-09 11:47 ` Markus Hoenicka
2014-10-09 11:55 ` Eli Zaretskii
2014-10-11 15:31 ` Ken Brown
2014-10-12 0:07 ` Markus Hoenicka
2014-10-20 10:59 ` Markus Hoenicka
2014-10-20 11:29 ` Ken Brown
2014-10-20 12:04 ` martin rudalics
2014-10-20 13:05 ` Ken Brown
2014-10-20 14:11 ` Markus Hoenicka
2014-10-20 14:37 ` Markus Hoenicka
2014-10-20 15:24 ` Eli Zaretskii
2014-10-20 15:29 ` Markus Hoenicka
2014-10-24 21:27 ` Ken Brown
2014-10-24 21:42 ` Markus Hoenicka
2014-12-03 12:43 ` Markus Hoenicka
2014-12-03 14:12 ` Ken Brown
2014-10-20 15:29 ` Eli Zaretskii
2014-10-07 16:05 ` Markus Hoenicka
2014-07-28 22:45 ` markus.hoenicka
2014-08-06 22:02 ` markus.hoenicka
2014-10-07 16:47 ` Achim Gratz
2014-10-07 18:43 ` Ken Brown
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=83fvfq2n40.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17753@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
--cc=markus.hoenicka@mhoenicka.de \
/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.