[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[O] bug#15888: 24.3.50; Eval-after-load eval'ed twice
From: |
Eli Zaretskii |
Subject: |
[O] bug#15888: 24.3.50; Eval-after-load eval'ed twice |
Date: |
Fri, 15 Nov 2013 10:42:23 +0200 |
> From: "Sebastien Vauban" <address@hidden>
> Cc: address@hidden, address@hidden, address@hidden
> Date: Fri, 15 Nov 2013 09:16:44 +0100
>
> > (gdb) break Fload
> > (gdb) commands
> > > p file
> > > xstring
> > > end
> > (gdb) r -Q
> >
> > Now, when the breakpoint breaks, you will see which file is being
> > loaded, and need just type "c RET" (or just "RET" after the first
> > time), and wait for "org-mode" to show in the output of the above
> > commands; then type "bt" to see who loaded it.
>
> Here it is.
Thanks.
Unfortunately, this:
> (gdb) No symbol "backtrace_list" in current context.
(whose reason I don't really understand) means that the Lisp backtrace
is absent from your data. Nevertheless, given this part:
> Breakpoint 3, Fload (file=60203985, noerror=57608218, nomessage=57608242,
> nosuffix=57608218, must_suffix=57608242) at ../../repo/src/lread.c:1048
> 1048 in ../../repo/src/lread.c
> $53 = 60203985
> $54 = (struct Lisp_String *) 0x396a3d0
> "org-loaddefs"
> (gdb)
> Continuing.
> [Thread 3332.0xaf4 exited with code 0]
>
> Breakpoint 3, Fload (file=59407297, noerror=57608218, nomessage=57608242,
> nosuffix=57608218, must_suffix=57608242) at ../../repo/src/lread.c:1048
> 1048 in ../../repo/src/lread.c
> $55 = 59407297
> $56 = (struct Lisp_String *) 0x38a7bc0
> "org"
It is quite clear that org-loaddefs has something to do with the
problem. As I understand it, Bastien just fixed that in Org trunk.
Thanks.
- [O] bug#15888: 24.3.50; Eval-after-load eval'ed twice, Glenn Morris, 2013/11/14
- [O] bug#15888: 24.3.50; Eval-after-load eval'ed twice, Sebastien Vauban, 2013/11/15
- [O] bug#15888: 24.3.50; Eval-after-load eval'ed twice,
Eli Zaretskii <=
- [O] bug#15888: 24.3.50; Eval-after-load eval'ed twice, Sebastien Vauban, 2013/11/15
- [O] bug#15888: 24.3.50; Eval-after-load eval'ed twice, Eli Zaretskii, 2013/11/15
- Message not available
- [O] bug#15888: 24.3.50; Eval-after-load eval'ed twice, Sebastien Vauban, 2013/11/15
- [O] bug#15888: 24.3.50; Eval-after-load eval'ed twice, Stefan Monnier, 2013/11/15
- [O] bug#15888: 24.3.50; Eval-after-load eval'ed twice, Sebastien Vauban, 2013/11/15
- [O] bug#15888: 24.3.50; Eval-after-load eval'ed twice, Eli Zaretskii, 2013/11/15
[O] bug#15888: 24.3.50; Eval-after-load eval'ed twice, Josh, 2013/11/16