From: Eli Zaretskii <eliz@gnu.org>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: 16518@debbugs.gnu.org
Subject: bug#16518: 24.3.50; Emacs hangs
Date: Wed, 22 Jan 2014 17:48:04 +0200 [thread overview]
Message-ID: <83lhy8f26j.fsf@gnu.org> (raw)
In-Reply-To: <86ob34ct0q.fsf@somewhere.org>
> From: "Sebastien Vauban" <sva-news@mygooglest.com>
> Date: Wed, 22 Jan 2014 09:36:37 +0100
>
> Emacs just hung this morning. I don't remember exactly which particular
> action I was doing, but that wasn't anything peculiar.
>
> I've attached GDB to the Emacs process, typed "thread apply all
> backtrace", "thread 1" and "finish" -- IIUC what I had to do...
You have 2 reader threads reading from network connections -- any idea
what connections are those and what is at the other end of those
connections?
Sorry, I see nothing else of any significance here, except that it's
some kind of deadlock.
next prev parent reply other threads:[~2014-01-22 15:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 8:36 bug#16518: 24.3.50; Emacs hangs Sebastien Vauban
2014-01-22 15:48 ` Eli Zaretskii [this message]
[not found] ` <83lhy8f26j.fsf-mXXj517/zsQ@public.gmane.org>
2014-01-22 16:14 ` Sebastien Vauban
2014-01-22 16:40 ` Eli Zaretskii
[not found] ` <mailman.12575.1390408874.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.12575.1390408874.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2014-01-22 19:52 ` Sebastien Vauban
2019-09-26 11:38 ` Stefan Kangas
2019-09-26 11:40 ` Stefan Kangas
2019-09-26 12:33 ` Michael Albinus
2019-09-26 12:46 ` Stefan Kangas
2019-09-26 16:07 ` Michael Albinus
2019-09-26 16:49 ` Stefan Kangas
2019-09-26 16:45 ` Stefan Kangas
2019-09-26 16:46 ` Stefan Kangas
[not found] <mailman.12552.1390379954.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.12552.1390379954.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2014-01-22 8:57 ` Sebastien Vauban
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=83lhy8f26j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16518@debbugs.gnu.org \
--cc=sva-news@mygooglest.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.