From: Richard Stallman <rms@gnu.org>
Cc: help-emacs-windows@gnu.org, eliz@elta.co.il, harald@maierh.de,
bug-gnu-emacs@gnu.org
Subject: Re: Current word on binaries
Date: Mon, 16 Feb 2004 14:52:28 -0500 [thread overview]
Message-ID: <E1Ason6-0008Pd-8U@fencepost.gnu.org> (raw)
In-Reply-To: <ud68hdfc0.fsf@jasonrumney.net> (message from Jason Rumney on 14 Feb 2004 12:18:39 +0000)
Since it is deep within the byte code interpreter it is difficult to
find what happened to get get the binding stack in that state.
You could disassemble the byte code and see if it is valid.
If it is valid, then debugging the byte code interpreter
might not be too hard. One could determine what the stack
level should be at certain points in the function, and add
debugging code to test the actual stack level at those points.
One could also do this by adding a bytecode instruction to test
the binding stack level, and adding a flag to make the compiler
generate these instructions. That would be a new debugging
feature in the compiler.
next prev parent reply other threads:[~2004-02-16 19:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <009901c3ec70$b3013940$6400a8c0@austin.rr.com>
[not found] ` <m3broc4fdc.fsf@ate.maierh>
2004-02-14 9:33 ` [h-e-w] Current word on binaries Harald Maier
2004-02-14 11:57 ` Jason Rumney
2004-02-14 12:06 ` Eli Zaretskii
2004-02-14 12:18 ` [h-e-w] " Jason Rumney
2004-02-16 19:52 ` Richard Stallman [this message]
2004-02-16 20:38 ` Jason Rumney
2004-02-17 6:50 ` [h-e-w] " Eli Zaretskii
2004-02-17 8:56 ` Jason Rumney
2004-02-17 19:03 ` Eli Zaretskii
2004-02-18 0:13 ` Jason Rumney
2004-02-18 6:11 ` Eli Zaretskii
2004-02-18 8:38 ` Richard Stallman
2004-02-18 10:39 ` [h-e-w] " Eli Zaretskii
2004-02-18 12:30 ` Harald Maier
2004-02-18 13:37 ` [h-e-w] " Jason Rumney
2004-02-18 14:28 ` Eli Zaretskii
2004-02-18 23:29 ` Jason Rumney
2004-02-18 13:43 ` Jason Rumney
2004-02-18 18:54 ` [h-e-w] " Eli Zaretskii
2004-02-14 13:18 ` Harald Maier
2004-02-14 13:37 ` Jason Rumney
2004-02-14 15:41 ` Harald Maier
2004-02-14 16:56 ` [h-e-w] " Eli Zaretskii
2004-02-14 17:24 ` Harald Maier
2004-02-14 17:49 ` Eli Zaretskii
2004-02-14 19:26 ` Harald Maier
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=E1Ason6-0008Pd-8U@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=eliz@elta.co.il \
--cc=harald@maierh.de \
--cc=help-emacs-windows@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).