From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Help with new Windows 98 crash
Date: Mon, 05 Dec 2022 16:52:28 +0200 [thread overview]
Message-ID: <83ilip9a37.fsf@gnu.org> (raw)
In-Reply-To: <87o7sindcl.fsf@yahoo.com> (message from Po Lu on Mon, 05 Dec 2022 22:18:18 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Date: Mon, 05 Dec 2022 22:18:18 +0800
>
> Emacs 30 (with unexec) is crashing on Windows 98 again, this time during
> GC.
I tried to build it on X, but the build fails:
xfns.c:46:10: fatal error: xcb/xcb_aux.h: No such file or directory
#include <xcb/xcb_aux.h>
^~~~~~~~~~~~~~~
compilation terminated.
can you please fix that? Then I could see if the problem is not only
Windows specific.
> I cannot find a version of GDB that reads DWARF generated by GCC 9,
> but here is the backtrace from GDB 5, which cannot read the debug
> information in emacs.exe:
>
> #0 0x011e5491
> #1 0x00a44b68
> #2 0x00160070
> #3 0x00343030
>
> the backtrace stops here, after which GDB complains it cannot access
> memory at address 0x30303030.
>
> addr2line says the first address belongs to line 606 of w32heap.c. The
> rest are garbage. Could it be that something is trying to free dumped
> memory?
Could be, I have no idea yet. But then FREEABLE_P doesn't do its job,
right?
> (and if anyone can find a copy of GDB that works on Windows 98 and can
> read the debuginfo, that would be best. Thanks in advance.)
Did you try building with -gstabs+ instead?
P.S. And maybe we should try fixing the problem that requires to use unexec
on Windows 9X to begin with.
next prev parent reply other threads:[~2022-12-05 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87o7sindcl.fsf.ref@yahoo.com>
2022-12-05 14:18 ` Help with new Windows 98 crash Po Lu
2022-12-05 14:52 ` Eli Zaretskii [this message]
2022-12-05 16:59 ` Eli Zaretskii
2022-12-06 1:29 ` Po Lu
2022-12-06 12:12 ` Eli Zaretskii
2022-12-06 12:53 ` Po Lu
2022-12-06 14:32 ` Eli Zaretskii
2022-12-07 0:59 ` Po Lu
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=83ilip9a37.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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 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).