From: Eli Zaretskii <eliz@gnu.org>
To: "Alpár Jüttner" <alpar@cs.elte.hu>
Cc: auctex-devel@gnu.org, 7053@debbugs.gnu.org,
Carsten Dominik <dominik@science.uva.nl>
Subject: bug#7053: Reftex is fully broken
Date: Sat, 18 Sep 2010 11:21:53 +0200 [thread overview]
Message-ID: <83mxrfz9se.fsf__27749.696703586$1284802865$gmane$org@gnu.org> (raw)
In-Reply-To: <1284783571.3343.8.camel@piko.site>
> From: Alpár Jüttner <alpar@cs.elte.hu>
> Cc: 7053@debbugs.gnu.org
> Date: Sat, 18 Sep 2010 06:19:31 +0200
>
> On Fri, 2010-09-17 at 18:20 +0200, Eli Zaretskii wrote:
> > > From: Alpár Jüttner <alpar@cs.elte.hu>
> > > Cc: 7053@debbugs.gnu.org
> > > Date: Fri, 17 Sep 2010 15:49:48 +0200
> > >
> > > Here is the GBD trace:
> >
> > Thanks. Unfortunately, this backtrace is not as useful as it could
> > be,
>
>
> I'm sorry. Here comes the lisp backtrace (when pressing C-c = ):
Thanks. It sounds like the problem is in reftex-what-macro. I'm
CC'ing the reftex author and maintainers in the hope that they can
find the culprit.
Failing that, perhaps you could do a "bzr bisect" to find the revision
which broke reftex.
Thanks.
>
> Lisp Backtrace:
> "forward-sexp" (0xbfffc9b4)
> "backward-sexp" (0xbfffcae4)
> ---Type <return> to continue, or q <return> to quit---
> "latex-backward-sexp-1" (0xbfffcc24)
> "byte-code" (0xbfffccd0)
> "latex-forward-sexp" (0xbfffcf64)
> "forward-sexp" (0xbfffd094)
> "byte-code" (0xbfffd140)
> "up-list" (0xbfffd3e4)
> "byte-code" (0xbfffd490)
> "byte-code" (0xbfffd6b0)
> "reftex-what-macro" (0xbfffd924)
> "reftex-label-location" (0xbfffda64)
> "reftex-label-info" (0xbfffdba4)
> "byte-code" (0xbfffdc60)
> "reftex-parse-from-file" (0xbfffdef4)
> "byte-code" (0xbfffdfa0)
> "reftex-do-parse" (0xbfffe174)
> "reftex-access-scan-info" (0xbfffe2a4)
> "reftex-toc" (0xbfffe414)
> "call-interactively" (0xbfffe5ac)
> (gdb)
>
> And here is another one (typing \ref{valami}, it also freezes reftex):
>
> Lisp Backtrace:
> "up-list" (0xbfffcea4)
> "byte-code" (0xbfffcf50)
> "byte-code" (0xbfffd170)
> "reftex-what-macro" (0xbfffd3e4)
> "reftex-what-macro-safe" (0xbfffd514)
> "reftex-view-crossref" (0xbfffd654)
> "byte-code" (0xbfffd700)
> "reftex-view-crossref-when-idle" (0xbfffda48)
> "apply" (0xbfffda44)
> "byte-code" (0xbfffdaf0)
> "timer-event-handler" (0xbfffdd94)
> (gdb)
>
> Regards,
> Alpar
>
>
next prev parent reply other threads:[~2010-09-18 9:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 9:41 bug#7053: Reftex is fully broken Alpár Jüttner
2010-09-17 11:52 ` Eli Zaretskii
2010-09-17 13:49 ` Alpár Jüttner
2010-09-17 16:20 ` Eli Zaretskii
2010-09-18 4:19 ` Alpár Jüttner
2010-09-18 9:21 ` Eli Zaretskii [this message]
2010-09-18 14:47 ` Stefan Monnier
2010-09-19 5:34 ` Alpár Jüttner
[not found] ` <83mxrfz9se.fsf@gnu.org>
2010-09-18 15:16 ` bug#7053: [AUCTeX-devel] " Ralf Angeli
[not found] ` <87vd635bfi.fsf@caeruleus.net>
2010-09-18 16:11 ` Stefan Monnier
[not found] ` <jwv62y39gts.fsf-monnier+emacs@gnu.org>
2010-09-18 16:28 ` Ralf Angeli
2010-09-19 8:48 ` Andreas Röhler
2010-09-20 23:40 ` Stefan Monnier
2010-09-19 5:24 ` Alpár Jüttner
2010-09-19 5:58 ` Eli Zaretskii
[not found] ` <E1OxCvN-0001nb-Jl@fencepost.gnu.org>
2010-09-19 6:42 ` Alpár Jüttner
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='83mxrfz9se.fsf__27749.696703586$1284802865$gmane$org@gnu.org' \
--to=eliz@gnu.org \
--cc=7053@debbugs.gnu.org \
--cc=alpar@cs.elte.hu \
--cc=auctex-devel@gnu.org \
--cc=dominik@science.uva.nl \
/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).