* Re: Strange entries in xbacktrace
2012-09-29 16:42 Strange entries in xbacktrace Eli Zaretskii
@ 2012-09-30 17:45 ` Eli Zaretskii
2012-09-30 20:06 ` Stefan Monnier
0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2012-09-30 17:45 UTC (permalink / raw)
To: emacs-devel
> Date: Sat, 29 Sep 2012 18:42:49 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> Since today (or maybe yesterday), I sometimes see strange entries in
> the Lisp backtrace. Like this, for example:
>
> Lisp Backtrace:
> 0xb6110000 Lisp type 0
>
> Is this expected? If so, how to interpret these?
Sounds like a bug, because I now get
Lisp Backtrace:
0x90310000 Lisp type 0
0xb2890000 Lisp type 0
0xaf790000 Lisp type 0
0x17190000 Lisp type 0
0x6dd10000 Lisp type 0
0x6f110000 Lisp type 0
0x15890360 Lisp type 4
0x81910000 Lisp type 0
where I should have seen a real Lisp backtrace, judging by the C
backtrace:
#5 0x0111bde9 in Fvertical_motion (lines=4, window=55121741) at indent.c:2063
#6 0x01015107 in Ffuncall (nargs=2, args=0x82ec04) at eval.c:2775
#7 0x0112585f in exec_byte_code (bytestr=20756017, vector=20756157,
maxdepth=20, args_template=55060506, nargs=0, args=0x0) at bytecode.c:899
#8 0x01015fc9 in funcall_lambda (fun=20755981, nargs=2, arg_vector=0x82ee68)
at eval.c:3004
#9 0x010154a3 in Ffuncall (nargs=3, args=0x82ee64) at eval.c:2821
#10 0x0112585f in exec_byte_code (bytestr=20755745, vector=20755853,
maxdepth=16, args_template=55060506, nargs=0, args=0x0) at bytecode.c:899
#11 0x01015fc9 in funcall_lambda (fun=20755693, nargs=4, arg_vector=0x82f0c8)
at eval.c:3004
#12 0x010154a3 in Ffuncall (nargs=5, args=0x82f0c4) at eval.c:2821
#13 0x0112585f in exec_byte_code (bytestr=20754401, vector=20754493,
maxdepth=24, args_template=55060506, nargs=0, args=0x0) at bytecode.c:899
#14 0x01015fc9 in funcall_lambda (fun=20754349, nargs=0, arg_vector=0x82f290)
at eval.c:3004
#15 0x010157db in apply_lambda (fun=20754349, args=55060506) at eval.c:2881
#16 0x010137b2 in eval_sub (form=59011630) at eval.c:2182
#17 0x0100f137 in Fprogn (args=59011622) at eval.c:359
#18 0x01012f24 in eval_sub (form=59011806) at eval.c:2085
#19 0x01012a86 in Feval (form=59011806, lexical=55060506) at eval.c:2002
#20 0x01015107 in Ffuncall (nargs=3, args=0x82f644) at eval.c:2775
#21 0x0112585f in exec_byte_code (bytestr=20723729, vector=20723845,
maxdepth=20, args_template=55060506, nargs=0, args=0x0) at bytecode.c:899
#22 0x01015fc9 in funcall_lambda (fun=20723677, nargs=2, arg_vector=0x82f8a4)
at eval.c:3004
#23 0x010154a3 in Ffuncall (nargs=3, args=0x82f8a0) at eval.c:2821
#24 0x01014296 in Fapply (nargs=2, args=0x82f940) at eval.c:2306
#25 0x0101481a in apply1 (fn=56823810, arg=59011246) at eval.c:2540
#26 0x01122a9e in Fcall_interactively (function=56823810,
record_flag=55060506, keys=55081901) at callint.c:377
#27 0x0101517c in Ffuncall (nargs=4, args=0x82fb80) at eval.c:2779
^ permalink raw reply [flat|nested] 3+ messages in thread