unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 11:10:44 +0200	[thread overview]
Message-ID: <4d8f70a5-9af9-6931-e46b-031f98918541@physik.fu-berlin.de> (raw)
In-Reply-To: <4c69025e-dcf4-3f6a-5c29-f529443173eb@cs.ucla.edu>

Hi Paul!

On 5/14/19 8:04 AM, Paul Eggert wrote:
> John Paul Adrian Glaubitz wrote:
>> Dumping under the name bootstrap-emacs.pdmp
>> dumping fingerprint: 3cb05906acd421bf706fa119445377d793ee7ffbbde4c79b70ca65fdb4bb625e
>> dump relocation out of range
> 
> I'd wildly guess it's a different problem. Try configuring Emacs for debugging
> (see etc/DEBUG) and then see if you can get a C backtrace just before it
> outputs "dump relocation out of range".

You seem to be correct. I just tried Michael's patch instead of yours and
emacs-git still crashes for me. On the other hand, backporting your current
patch to the 26 branch fixes the bug for me for emacs26.

Thus, could you backport your patch to the 26 branch?

Thanks,
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





  reply	other threads:[~2019-05-14  9:10 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
2019-05-14  6:04     ` Paul Eggert
2019-05-14  9:10       ` John Paul Adrian Glaubitz [this message]
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=4d8f70a5-9af9-6931-e46b-031f98918541@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).