unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 35784@debbugs.gnu.org, Marc Munro <marc@bloodnok.com>
Subject: bug#35784: emacs 26 crash
Date: Sat, 18 May 2019 10:19:22 -0400	[thread overview]
Message-ID: <87woindevp.fsf@gmail.com> (raw)
In-Reply-To: <b1cbb116-8d9c-e07d-a5f5-9510e7026d39@gmx.at> (martin rudalics's message of "Sat, 18 May 2019 16:03:05 +0200")

martin rudalics <rudalics@gmx.at> writes:

>> I'm able to reproduce using the latest emacs-26 branch (I don't have the
>> point releases checked out at the moment), both lucid and gtk3 builds.
>> It doesn't reproduce using master, there is a Lisp error (Symbol's
>> definition is void: new-frame) that interferes.
>
> Could you try with 'make-frame' instead of 'new-frame' (or defaliasing
> 'new-frame' to 'make-frame')?  Here I can't reproduce the crash with
> Emacs 27 and I'm a bit too lazy to delve deeper on my broken systems.

Ah, right, adding

    (defalias 'new-frame 'make-frame)

lets it reproduce on master too.





  reply	other threads:[~2019-05-18 14:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-17 20:54 bug#35784: emacs 26 crash Marc Munro
2019-05-18  6:19 ` Eli Zaretskii
2019-05-18  9:39   ` Bhavin Gandhi
2019-05-18 12:09     ` Eli Zaretskii
2019-05-18 12:16   ` Noam Postavsky
2019-05-18 13:03     ` Eli Zaretskii
2019-05-18 14:03     ` martin rudalics
2019-05-18 14:19       ` Noam Postavsky [this message]
2019-05-18 15:39         ` Eli Zaretskii
2019-05-18 17:30           ` martin rudalics
2019-05-18 17:43             ` Eli Zaretskii
2019-05-19  2:54             ` Noam Postavsky
2019-05-19  4:51               ` Eli Zaretskii
2019-05-19  6:40                 ` martin rudalics
2019-05-19 17:11                   ` Noam Postavsky
2019-05-19 17:59                     ` Eli Zaretskii
2019-05-20 18:27                       ` Noam Postavsky
2019-05-19 23:57 ` bug#35784: Just built from head: it seems to be fixed Marc Munro

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=87woindevp.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=35784@debbugs.gnu.org \
    --cc=marc@bloodnok.com \
    --cc=rudalics@gmx.at \
    /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).