emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Thu, 20 Mar 2014 18:38:31 +0200	[thread overview]
Message-ID: <8338ic9660.fsf__19889.5982037813$1395333602$gmane$org@gnu.org> (raw)
In-Reply-To: <8661n9qi0r.fsf@somewhere.org>

> From: Sebastien Vauban <sva-news@mygooglest.com>
> Cc: 17040@debbugs.gnu.org
> Date: Thu, 20 Mar 2014 11:30:28 +0100
> 
> > 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.
> 
> I still have that GDB session open... So I just did it:
> 
> --8<---------------cut here---------------start------------->8---
> (gdb) source ~/.gdbinit
> SIGINT is used by the debugger.
> Are you sure you want to change it? (y or n) [answered Y; input not from terminal]
> Warning: /cygdrive/c/Program Files (x86)/emacs-r114715-20131019-w32/bin/../lwlib: No such file or directory.
> Environment variable "DISPLAY" not defined.
> TERM = xterm-256color
> (gdb) ~/.gdbinit:1261: Error in sourced command file:
> PC register is not available
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
That session is ruined, so it won't help.  This happened because you
typed "finish" after attaching the debugger; next time please don't do
that.

Since you say these problems are quite frequent, please produce the
Lisp backtrace next time this happens.

Thanks.

  reply	other threads:[~2014-03-20 16:39 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 ` bug#17040: 24.3.50; Emacs + Org mode hangs Eli Zaretskii
2014-03-19 17:07 ` 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 [this message]
     [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='8338ic9660.fsf__19889.5982037813$1395333602$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).