From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Paul Eggert <eggert@cs.ucla.edu>, 35711@debbugs.gnu.org
Cc: Andreas Schwab <schwab@suse.de>,
Michael Karcher <debian@mkarcher.dialup.fu-berlin.de>
Subject: bug#35711: emacs crashes on m68k after d2f1971dd5
Date: Tue, 14 May 2019 08:01:52 +0200 [thread overview]
Message-ID: <5e02ba77-bc93-ca99-003a-8b72f742bc7b@physik.fu-berlin.de> (raw)
In-Reply-To: <98a8bb69-486e-20b2-891d-65015bab9579@cs.ucla.edu>
Hi Paul!
On 5/13/19 9:47 PM, Paul Eggert wrote:
> Thanks for the bug report. Please try the attached, more-general patch,
> which I've installed on master. I suppose I should backport it to the
> emacs-26 branch if it works for you.
I just checked out emacs from git and started a test build on m68k. The
original crahs no longer shows, but I'm running into this problem now
which I don't know whether it's related:
Finding pointers to doc strings...
Finding pointers to doc strings...done
Dumping under the name bootstrap-emacs.pdmp
dumping fingerprint: 3cb05906acd421bf706fa119445377d793ee7ffbbde4c79b70ca65fdb4bb625e
dump relocation out of range
make[1]: *** [Makefile:808: bootstrap-emacs.pdmp] Error 255
make[1]: Leaving directory '/usr/src/emacs/src'
make: *** [Makefile:424: src] Error 2
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2019-05-14 6:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 12:15 bug#35711: emacs crashes on m68k after d2f1971dd5 John Paul Adrian Glaubitz
2019-05-13 19:47 ` Paul Eggert
2019-05-14 6:01 ` John Paul Adrian Glaubitz [this message]
2019-05-14 6:04 ` Paul Eggert
2019-05-14 9:10 ` John Paul Adrian Glaubitz
2019-05-14 18:10 ` Paul Eggert
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=5e02ba77-bc93-ca99-003a-8b72f742bc7b@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=35711@debbugs.gnu.org \
--cc=debian@mkarcher.dialup.fu-berlin.de \
--cc=eggert@cs.ucla.edu \
--cc=schwab@suse.de \
/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).