From: Eli Zaretskii <eliz@gnu.org>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: 17040@debbugs.gnu.org
Subject: bug#17040: 24.3.50; Emacs + Org mode hangs
Date: Wed, 19 Mar 2014 19:03:32 +0200 [thread overview]
Message-ID: <8338ie9l3v.fsf__31867.4779883169$1395248698$gmane$org@gnu.org> (raw)
In-Reply-To: <86lhw65j8f.fsf@somewhere.org>
> From: Sebastien Vauban <sva-news@mygooglest.com>
> Date: Wed, 19 Mar 2014 15:57:36 +0100
>
> Anyway, here's the backtrace I got:
Thanks for the effort, but as I said several times, such backtraces
are not useful without the Lisp backtrace part. All I can say from
this backtrace is that you were deep inside some hook stored in
before-change-functions; that hook was invoked because you inserted
something into a buffer. That is all.
What we need is names of some Lisp functions, preferably from Org,
that we could then examine in order to look for potential infloops.
That's impossible without Lisp backtrace. To get that, you need the
.gdbinit file, and you need to instruct GDB to read it by using the
'source' command.
next parent reply other threads:[~2014-03-19 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86lhw65j8f.fsf@somewhere.org>
2014-03-19 17:03 ` Eli Zaretskii [this message]
2014-03-19 17:07 ` bug#17040: 24.3.50; Emacs + Org mode hangs Juanma Barranquero
[not found] ` <CAAeL0SReZsOA5nfMfkX4WivSgVacRw9jPbQpCzkXbjeXux4xYw__6285.99562119252$1395330721$gmane$org-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-20 15:53 ` Sebastien Vauban
[not found] ` <8338ie9l3v.fsf@gnu.org>
[not found] ` <8338ie9l3v.fsf-mXXj517/zsQ@public.gmane.org>
2014-03-20 10:30 ` Sebastien Vauban
2014-03-20 16:38 ` Eli Zaretskii
[not found] ` <mailman.17657.1395333567.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.17657.1395333567.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2014-03-20 17:01 ` 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
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='8338ie9l3v.fsf__31867.4779883169$1395248698$gmane$org@gnu.org' \
--to=eliz@gnu.org \
--cc=17040@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 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).