From: Eli Zaretskii <eliz@gnu.org>
To: luangruo@yahoo.com
Cc: 52295@debbugs.gnu.org
Subject: bug#52295: 28.0.90; Killing text results in coding system complaint
Date: Sat, 18 Dec 2021 20:30:08 +0200 [thread overview]
Message-ID: <83mtkxahqn.fsf@gnu.org> (raw)
In-Reply-To: <83bl1ecst4.fsf@gnu.org> (message from Eli Zaretskii on Sat, 18 Dec 2021 08:48:07 +0200)
> Date: Sat, 18 Dec 2021 08:48:07 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 52295@debbugs.gnu.org
>
> If it's a real crash, you could use the Windows Event log to find out
> the address where it crashes, and then use GDB on another system to
> see where that address is in the sources (but the address printed by
> Windows needs to be "translated" into addresses that you submit to GDB
> by adding some constant, AFAIR).
>
> The other alternative is to insert many fprintf's to stderr into the
> sources, and use that to determine where it crashes.
>
> If it's an abort, then saying NO to the dialog will produce an
> emacs_backtrace.txt file with addresses of the backtrace, which you
> could take to another Windows system and use addr2line (from Binutils)
> to recover the file names, function names, and line numbers that
> correspond to the addresses; see the node "Crashing" in the Emacs
> manual for how to do that.
Btw, there's one more alternative: to debug Emacs on Windows 9X
remotely, via gdbserver. Did you try that? The advantage is that
gdbserver is a much smaller and simpler program, so chances are it
will be able to run on Windows 9X. GDB itself will run on a different
system (could even be GNU/Linux, if you have GDB that was built to
support debugging Windows PE executables), where all the problems of
running a modern GDB don't exist. You just need the target system to
be connected to a network, so that GDB and gdbserver could
communicate.
next prev parent reply other threads:[~2021-12-18 18:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <875ys3sgfv.fsf.ref@yahoo.com>
2021-12-05 6:40 ` bug#52295: 28.0.90; Killing text results in coding system complaint luangruo--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-05 8:45 ` Eli Zaretskii
2021-12-05 8:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-05 9:12 ` Eli Zaretskii
2021-12-05 9:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-06 12:33 ` Eli Zaretskii
2021-12-07 3:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-07 5:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-07 7:33 ` Eli Zaretskii
2021-12-07 9:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-07 10:07 ` Eli Zaretskii
2021-12-07 10:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-07 10:50 ` Eli Zaretskii
2021-12-07 14:05 ` Eli Zaretskii
2021-12-12 10:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-12 11:22 ` Eli Zaretskii
2021-12-12 12:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-12 13:31 ` Eli Zaretskii
2021-12-13 0:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-13 3:23 ` Eli Zaretskii
2021-12-18 0:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-18 6:48 ` Eli Zaretskii
2021-12-18 18:30 ` Eli Zaretskii [this message]
2021-12-19 0:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-27 9:09 ` bug#52295: windows 98: " Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83mtkxahqn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52295@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
/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.