From: Dan Jacobson <jidanni@dman.ddts.net>
Subject: Re: debug-on-call
Date: 04 Feb 2003 09:11:12 +0800 [thread overview]
Message-ID: <87adhconnz.fsf@jidanni.org> (raw)
In-Reply-To: 3E3E9E3B.5040000@ihs.com
>>>>> "K" == Kevin Rodgers <kevin.rodgers@ihs.com> writes:
K> Dan Jacobson wrote:
>> I wanted to have emacs stop if it ever called a function, but no:
>> debug-on-entry: Function base64-encode-region is a primitive
>>
>> I don't need to debug inside that function. All I wanted was to see a
>> backtrace so I can tell the layers of stuff calling that function.
K> (defadvice base64-encode-region (before debug activate)
K> "Debug (when called from an Emacs Lisp function)."
K> (debug))
OK, maybe this could be the guts of the new debug-on-call function, or
at least documented as what to do when debug-on-entry isn't usable...
Of course an antidote should also be provided to turn it off.
P.S. Kev, your References:
<mailman.1280.1044050572.21513.bug-gnu-emacs@gnu.org> does not give my
original post the fame and glory of its original Message-ID causing
its thread to be broken 'in many newsreaders'. Did you try reading
this group via NNTP of gmane.org for maximal comfort?
--
http://jidanni.org/ Taiwan(04)25854780
next prev parent reply other threads:[~2003-02-04 1:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1280.1044050572.21513.bug-gnu-emacs@gnu.org>
2003-02-03 16:52 ` debug-on-call Kevin Rodgers
2003-02-04 1:11 ` Dan Jacobson [this message]
2003-02-18 18:15 ` debug-on-call Kevin Rodgers
2003-02-19 2:48 ` message id got changed by mailman? Dan Jacobson
2003-02-19 22:09 ` Kevin Rodgers
2003-02-22 1:24 ` Dan Jacobson
2003-02-04 15:42 ` debug-on-call Richard Stallman
[not found] ` <mailman.1383.1044374904.21513.bug-gnu-emacs@gnu.org>
2003-02-13 19:25 ` debug-on-call Alexander Pohoyda
2003-01-31 19:03 debug-on-call Dan Jacobson
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=87adhconnz.fsf@jidanni.org \
--to=jidanni@dman.ddts.net \
/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).