From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 19606@debbugs.gnu.org, fni-news@pirilampo.org
Subject: bug#19606: 24.4; Emacs hangs when editing a 5-line Org file
Date: Fri, 16 Jan 2015 10:24:51 +0200 [thread overview]
Message-ID: <83mw5j2kvg.fsf__14138.8225405992$1421396728$gmane$org@gnu.org> (raw)
In-Reply-To: <54B82BF2.8050504@yandex.ru>
> Date: Fri, 16 Jan 2015 00:06:58 +0300
> From: Dmitry Gutov <dgutov@yandex.ru>
> CC: 19606@debbugs.gnu.org
>
> On 01/15/2015 09:14 PM, Eli Zaretskii wrote:
>
> > But you didn't even show the backtrace from the main (a.k.a. "Lisp")
> > thread. Your backtrace is from thread 15, whereas the main thread is
> > thread 1.
>
> The output is from 'thread apply all backtrace', AFAICS.
No, the output is only from threads 15 and 14. The command "thread
apply all backtrace" was indeed issued, but Emacs crashed or exited
abnormally while producing the Lisp-level backtrace for thread 14:
[Inferior 1 (process 1204) exited with code 01]
(gdb) The program being debugged exited while in a function called from GDB.
Evaluation of the expression containing the function
(backtrace_top) will be abandoned.
Therefore that command didn't produce backtraces of the rest of the
threads.
The backtraces shown are not interesting: thread 15 is a thread
created by Windows for attaching the debugger, so it doesn't belong to
Emacs; and thread 14 is the file-notification thread started by
w32notify.c, which simply sleeps waiting for file events. So the
interesting information from the main thread is not presented, and
it's therefore impossible to tell where and why Emacs hanged.
Typing "thread 1" explicitly right after attaching to the process
might have produce the C-level backtrace for the main thread. It is a
good thing to do in any case when attaching to Emacs process that's in
trouble.
> On the other hand, it's not 'bt full' or `xbacktrace', which
> report-emacs-bug asks to call.
"xbacktrace" is automatically called after the C-level backtrace, when
you start GDB from the Emacs's src directory, where .gdbinit file
arranges for that. That's why you see this part in the OP:
Lisp Backtrace:
"redisplay_internal (C function)" (0x1407e78)
"redisplay" (0x88f254)
"sit-for" (0x88f3a8)
"flyspell-check-word-p" (0x88f4f8)
"byte-code" (0x88f610)
"flyspell-post-command-hook" (0x88f844)
next prev parent reply other threads:[~2015-01-16 8:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86mw5kktly.fsf@example.com>
[not found] ` <mailman.17962.1421338747.1147.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.17962.1421338747.1147.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2015-01-15 18:04 ` bug#19606: 24.4; Emacs hangs when editing a 5-line Org file Fabrice Niessen
[not found] ` <86lhl32a5e.fsf@example.com>
2015-01-15 18:14 ` Eli Zaretskii
[not found] ` <83oapz3o89.fsf@gnu.org>
2015-01-15 21:06 ` Dmitry Gutov
2015-01-15 21:37 ` Glenn Morris
[not found] ` <54B82BF2.8050504@yandex.ru>
2015-01-16 8:24 ` Eli Zaretskii [this message]
[not found] ` <mailman.17998.1421396712.1147.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.17998.1421396712.1147.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2015-01-16 11:27 ` Fabrice Niessen
[not found] ` <mailman.18013.1421407690.1147.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.18013.1421407690.1147.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2015-01-16 11:31 ` Fabrice Niessen
[not found] ` <867fwnynhn.fsf@example.com>
2015-01-16 11:49 ` Eli Zaretskii
[not found] ` <83wq4n0wup.fsf@gnu.org>
[not found] ` <83wq4n0wup.fsf-mXXj517/zsQ@public.gmane.org>
2015-01-16 12:04 ` Fabrice Niessen
[not found] ` <86ppafx77z.fsf@example.com>
2015-01-16 15:31 ` Eli Zaretskii
[not found] ` <83twzq213t.fsf@gnu.org>
[not found] ` <86lhl237cl.fsf@example.com>
2015-01-16 20:14 ` Eli Zaretskii
[not found] ` <83bnly1o0w.fsf@gnu.org>
2015-01-16 22:29 ` Glenn Morris
2015-01-28 20:41 ` Dani Moncayo
[not found] ` <83twzq213t.fsf-mXXj517/zsQ@public.gmane.org>
2015-01-16 18:31 ` Fabrice Niessen
2015-01-30 16:07 ` Fabrice Niessen
2015-01-31 8:25 ` Eli Zaretskii
[not found] ` <83386rl5kh.fsf@gnu.org>
2016-12-07 19:26 ` Glenn Morris
[not found] ` <6cy4p3209r.fsf@fencepost.gnu.org>
2015-01-16 8:26 ` Eli Zaretskii
[not found] ` <mailman.17999.1421396829.1147.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.17999.1421396829.1147.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2015-01-16 11:16 ` Fabrice Niessen
2015-01-16 11:30 ` Eric Abrahamsen
2015-01-16 11:37 ` Fabrice Niessen
2015-01-16 20:11 ` Achim Gratz
[not found] ` <86bnlzynzp.fsf@example.com>
2015-01-16 11:44 ` Eli Zaretskii
[not found] ` <83zj9j0x2s.fsf@gnu.org>
[not found] ` <83zj9j0x2s.fsf-mXXj517/zsQ@public.gmane.org>
2015-01-16 11:58 ` Fabrice Niessen
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='83mw5j2kvg.fsf__14138.8225405992$1421396728$gmane$org@gnu.org' \
--to=eliz@gnu.org \
--cc=19606@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=fni-news@pirilampo.org \
/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/org-mode.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).