From: John Wiegley <jwiegley@gmail.com>
To: Maneesh Yadav <maneeshkyadav@gmail.com>
Cc: 21965@debbugs.gnu.org
Subject: bug#21965: 24.5; Emacs freezes when canceling at open file
Date: Mon, 23 Nov 2015 14:17:17 -0800 [thread overview]
Message-ID: <m2mvu4e4ya.fsf@newartisans.com> (raw)
In-Reply-To: <CAPsivR9LptbM9M=s73SttSBNT0-Y0LOe4wBf9MeY6Gs4_S13MQ@mail.gmail.com> (Maneesh Yadav's message of "Mon, 23 Nov 2015 13:29:24 -0800")
>>>>> Maneesh Yadav <maneeshkyadav@gmail.com> writes:
> Flog me if I am not doing this right. Seems that +debug on macports is the
> easy to make debug compiles (an old thread seemed to suggest that macports
> rejected this idea...but I guess it was eventually accepted). So installed
> emacs +debug and reproduced the crash, attached to emacs via lldb and got
> this backtrace (which looks a lot like the previous, can I provide better
> info somehow?):
We're still missing file and line numbers for the Emacs code, which is odd.
But not terribly important, since the lockup is happening inside glib, it
appears.
> frame #3: 0x00000001009db284
> libglib-2.0.0.dylib`g_main_context_acquire + 42
So, here's that function, more or less:
gboolean
g_main_context_acquire (GMainContext *context)
{
gboolean result = FALSE;
GThread *self = G_THREAD_SELF;
if (context == NULL)
context = g_main_context_default ();
LOCK_CONTEXT (context);
/* ... */
}
We're blocked waiting on the context. The question then being: who else has
that context? Is it another Emacs thread?
Eli, does this ring any bells?
John
next prev parent reply other threads:[~2015-11-23 22:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 19:18 bug#21965: 24.5; Emacs freezes when canceling at open file Maneesh Yadav
2015-11-20 21:37 ` John Wiegley
2015-11-20 21:47 ` Maneesh Yadav
2015-11-20 21:55 ` John Wiegley
2015-11-20 22:07 ` Maneesh Yadav
2015-11-20 22:45 ` Maneesh Yadav
2015-11-20 23:26 ` John Wiegley
2015-11-20 23:32 ` Maneesh Yadav
2015-11-20 23:54 ` John Wiegley
2015-11-21 1:46 ` Maneesh Yadav
2015-11-21 7:29 ` Eli Zaretskii
2015-11-22 5:11 ` John Wiegley
2015-11-22 5:15 ` Maneesh Yadav
2015-11-23 21:29 ` Maneesh Yadav
2015-11-23 22:17 ` John Wiegley [this message]
2015-11-24 0:30 ` Maneesh Yadav
2015-11-24 3:39 ` Eli Zaretskii
2015-11-24 3:34 ` Eli Zaretskii
2015-11-24 3:39 ` John Wiegley
2015-11-24 22:51 ` Maneesh Yadav
2015-11-24 22:58 ` Maneesh Yadav
2015-11-25 1:02 ` John Wiegley
2015-11-25 1:15 ` Maneesh Yadav
2015-11-25 1:38 ` John Wiegley
2015-11-25 1:46 ` Maneesh Yadav
2015-11-25 1:50 ` John Wiegley
2015-11-25 18:49 ` Maneesh Yadav
2015-11-25 18:59 ` John Wiegley
2016-02-18 21:46 ` Maneesh Yadav
2016-02-20 2:40 ` John Wiegley
2020-08-31 2:11 ` Stefan Kangas
2020-08-31 2:25 ` Maneesh Yadav
2020-08-31 13:54 ` Stefan Kangas
2015-11-20 22:01 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2mvu4e4ya.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=21965@debbugs.gnu.org \
--cc=maneeshkyadav@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).