From: npostavs@users.sourceforge.net
To: Werner LEMBERG <wl@gnu.org>
Cc: 8108@debbugs.gnu.org
Subject: bug#8108: 24.0.50; debugging pre-write-conversion in define-coding-system
Date: Sat, 10 Dec 2016 10:12:01 -0500 [thread overview]
Message-ID: <87k2b7es3i.fsf@users.sourceforge.net> (raw)
In-Reply-To: <20110224.084058.453347781.wl@gnu.org> (Werner LEMBERG's message of "Thu, 24 Feb 2011 08:40:58 +0100 (CET)")
Werner LEMBERG <wl@gnu.org> writes:
> ----------------------------------------------------------------------
>
>
> I'm updating my cjk-enc.el package (part of the CJK bundle for LaTeX)
> to replace make-coding-system with define-coding-system. However, I
> can't debug it.
>
> In previous Emacs versions, I've instrumented the function used for
> the pre-write-conversion hook, and the debugger correctly stops there.
> However, with a recent Emacs (bzr version 103411 from today) this no
> longer works. Is this a bug? Am I missing something?
Not sure which version this corresponds to, but in [1]
encode_coding_object started using safe_call instead of a plain call to
run the pre-write-conversion function. safe_call intentionally disables
the debugger while running the function:
/* Use Qt to ensure debugger does not run,
so there is no possibility of wanting to redisplay. */
val = internal_condition_case_n (Ffuncall, nargs, args, Qt,
safe_eval_handler);
[1]: Tue Mar 29 00:34:38 2005
http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=d4850d674381d9493c94d30f8944a765e79537eb
(decode_coding_object): Use safe_call1 instead of call1.
(encode_coding_object): Use safe_call instead of call2.
next prev parent reply other threads:[~2016-12-10 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 7:40 bug#8108: 24.0.50; debugging pre-write-conversion in define-coding-system Werner LEMBERG
2011-04-21 5:48 ` Werner LEMBERG
2011-04-21 9:06 ` Eli Zaretskii
2011-12-26 20:03 ` Werner LEMBERG
2011-12-27 3:52 ` Eli Zaretskii
2016-12-10 15:12 ` npostavs [this message]
2016-12-10 17:44 ` Werner LEMBERG
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2b7es3i.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=8108@debbugs.gnu.org \
--cc=wl@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.