From: "Stefan Monnier" <monnier+gnu.emacs.help/news/@flint.cs.yale.edu>
Subject: Re: menu-bar-update-hook performance problems
Date: 10 Mar 2003 14:53:43 -0500 [thread overview]
Message-ID: <5lel5fngl4.fsf@rum.cs.yale.edu> (raw)
In-Reply-To: 87d6l8ozsi.fsf@nodewarrior.org
>>>>> "Dan" == Dan Debertin <airboss@nodewarrior.org> writes:
> (lambda ()
> (save-excursion
> (set-buffer (get-buffer-create "*temp-trace*"))
> (insert (prin1-to-string (backtrace))))))
> But, sadly, the backtraces I get out of it (and boy, do I ever get
> backtraces) stop at 'run-hooks'. Perhaps I will advise run-hooks.
It's probably because the hook is run from the C code, so there
is no previous elisp function on the stack. You'll need
to debug it at the C level, I'm afraid.
Stefan
next prev parent reply other threads:[~2003-03-10 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 18:04 menu-bar-update-hook performance problems Dan Debertin
2003-03-03 20:04 ` Kai Großjohann
2003-03-03 22:23 ` Dan Debertin
2003-03-04 8:07 ` Kai Großjohann
2003-03-04 15:44 ` Dan Debertin
2003-03-04 17:55 ` Kai Großjohann
2003-03-10 19:53 ` Stefan Monnier [this message]
2003-03-04 8:06 ` Kai Großjohann
2003-03-04 20:06 ` Kevin Rodgers
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=5lel5fngl4.fsf@rum.cs.yale.edu \
--to=monnier+gnu.emacs.help/news/@flint.cs.yale.edu \
/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.
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).