From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [drew.adams@oracle.com: RE: weird defadvice bug with byte-compilation]
Date: Wed, 14 Dec 2005 21:38:37 +0200 [thread overview]
Message-ID: <ud5jzqxj6.fsf@gnu.org> (raw)
In-Reply-To: <E1EmJeQ-0002d5-8y@fencepost.gnu.org> (rms@gnu.org)
> From: "Richard M. Stallman" <rms@gnu.org>
> CC: emacs-devel@gnu.org
> Date: Tue, 13 Dec 2005 18:33:42 -0500
>
> > #38 0x0112ad43 in single_menu_item (key=29457273, item=525205504,
> > pending_maps_ptr=0x82d09c, notreal=0, maxdepth=9) at w32menu.c:522
> > #39 0x0112b02e in single_keymap_panes (keymap=29457273, pane_name=2089878893,
> > prefix=9, notreal=17085537, maxdepth=24812917) at w32menu.c:468
> > (More stack frames follow...)
> >
> > You cut it off just as it's starting to get interesting!
>
> Tell me what you want to know or see, and I will make sure it's not
> cut off.
>
> Where does it come from in Fx_create_frame?
>
> If there are two frames that call Fx_create_frame, I need
> to see both.
Unfortunately, I cannot show this in the C traceback, because GDB
chokes on the next stack frame:
#39 0x0112ae03 in single_menu_item (key=28443961, item=0,
pending_maps_ptr=0x82d09c, notreal=0, maxdepth=9) at w32menu.c:522
#40 0x0112b0ee in single_keymap_panes (keymap=28443961, pane_name=0, prefix=9,
notreal=17085537, maxdepth=24660221) at w32menu.c:468
#41 0x00000000 in ?? () from
#42 0x00000009 in ?? ()
#43 0x0104b461 in parse_menu_item (item=480, notreal=8573128,
inmenubar=18001130) at keyboard.c:7376
#44 0x01c76008 in ?? ()
#45 0x000001e0 in ?? ()
#46 0x0082d0c8 in ?? ()
#47 0x0112acea in grow_menu_items () at w32menu.c:329
#48 0x01011575 in x_y_to_hpos_vpos (w=0x1b20539, x=Cannot access memory at address 0x1b016c00) at xdisp.c:1005
Cannot access memory at address 0x1b016c14
But the Lisp traceback clearly shows the recursive call:
"x-create-frame"
"x-create-frame-with-faces"
"make-frame"
"special-display-popup-frame"
"pop-to-buffer"
"byte-code"
"debug"
"and"
"x-create-frame"
"x-create-frame-with-faces"
"make-frame"
"special-display-popup-frame"
"display-buffer"
"display-warning"
"byte-compile-log-warning"
"byte-compile-warn"
"byte-compile-variable-ref"
"byte-compile-form"
"byte-compile-body"
"byte-compile-let"
"byte-compile-form"
"byte-compile-top-level"
"byte-compile-lambda"
0x1c2cf24 PVEC_COMPILED
"funcall"
"byte-compile"
"ad-compile-function"
"ad-activate-advised-definition"
"ad-activate"
"byte-code"
"require"
"eval"
"eval-last-sexp-1"
"eval-last-sexp"
"call-interactively"
I think the recursion happens when Emacs builds the menu bar for the
new frame. The C functions that build menu items, which show in the C
traceback, are an evidence to that effect.
next prev parent reply other threads:[~2005-12-14 19:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 2:36 [drew.adams@oracle.com: RE: weird defadvice bug with byte-compilation] Richard Stallman
2005-12-07 18:55 ` Chong Yidong
2005-12-08 4:53 ` Richard M. Stallman
2005-12-08 16:14 ` Drew Adams
2005-12-09 13:17 ` Eli Zaretskii
2005-12-09 14:07 ` Chong Yidong
2005-12-09 18:37 ` [drew.adams@oracle.com: RE: weird defadvice bug withbyte-compilation] Drew Adams
2005-12-10 4:14 ` [drew.adams@oracle.com: RE: weird defadvice bug with byte-compilation] Richard M. Stallman
2005-12-11 18:17 ` [drew.adams@oracle.com: RE: weird defadvice bug withbyte-compilation] Drew Adams
2005-12-12 5:23 ` Richard M. Stallman
2005-12-12 5:40 ` [drew.adams@oracle.com: RE: weird defadvice bugwithbyte-compilation] Drew Adams
2005-12-13 3:14 ` Richard M. Stallman
2005-12-13 3:52 ` [drew.adams@oracle.com: RE: weird defadvicebugwithbyte-compilation] Drew Adams
2005-12-13 23:33 ` Richard M. Stallman
2005-12-14 1:05 ` [drew.adams@oracle.com: RE: weirddefadvicebugwithbyte-compilation] Drew Adams
2005-12-14 1:24 ` Johan Bockgård
2005-12-14 3:41 ` [drew.adams@oracle.com: Drew Adams
2005-12-14 3:45 ` [drew.adams@oracle.com:RE:weirddefadvicebugwithbyte-compilation] Drew Adams
2005-12-14 17:17 ` [drew.adams@oracle.com: Johan Bockgård
2005-12-14 21:29 ` [drew.adams@oracle.com:RE:weirddefadvicebugwithbyte-compilation] Drew Adams
2005-12-14 23:43 ` [drew.adams@oracle.com:RE:weirddefadvicebugwithbyte-compilation] Johan Bockgård
2005-12-15 1:46 ` [drew.adams@oracle.com:RE:weirddefadvicebugwithbyte-compilation] Drew Adams
2005-12-11 20:21 ` [drew.adams@oracle.com: RE: weird defadvice bug with byte-compilation] Eli Zaretskii
2005-12-11 21:35 ` [drew.adams@oracle.com: RE: weird defadvice bug withbyte-compilation] Drew Adams
2005-12-12 5:52 ` Eli Zaretskii
2005-12-12 6:11 ` [drew.adams@oracle.com: RE: weird defadvice bugwithbyte-compilation] Drew Adams
2005-12-12 6:44 ` [drew.adams@oracle.com: RE: weird defadvicebugwithbyte-compilation] Drew Adams
2005-12-12 21:22 ` Eli Zaretskii
2005-12-12 21:53 ` [drew.adams@oracle.com: RE: weirddefadvicebugwithbyte-compilation] Drew Adams
2005-12-13 4:30 ` Eli Zaretskii
2005-12-13 4:59 ` [drew.adams@oracle.com: Drew Adams
2005-12-12 5:23 ` [drew.adams@oracle.com: RE: weird defadvice bug with byte-compilation] Richard M. Stallman
2005-12-12 6:11 ` Eli Zaretskii
2005-12-13 3:14 ` Richard M. Stallman
2005-12-13 4:39 ` Eli Zaretskii
2005-12-13 23:33 ` Richard M. Stallman
2005-12-14 19:38 ` Eli Zaretskii [this message]
2005-12-15 2:09 ` Richard M. Stallman
2005-12-15 4:46 ` Eli Zaretskii
2005-12-16 1:51 ` Richard M. Stallman
2005-12-16 19:48 ` Eli Zaretskii
2005-12-16 20:14 ` Eli Zaretskii
2005-12-17 1:05 ` Richard M. Stallman
2005-12-17 8:29 ` Eli Zaretskii
2005-12-17 23:59 ` Richard M. Stallman
-- strict thread matches above, loose matches on Subject: below --
2005-11-28 4:46 Richard M. Stallman
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=ud5jzqxj6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).