unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Marc Munro <marc@bloodnok.com>
Cc: 35784@debbugs.gnu.org
Subject: bug#35784: emacs 26 crash
Date: Sat, 18 May 2019 09:19:22 +0300	[thread overview]
Message-ID: <83ftpc9ted.fsf@gnu.org> (raw)
In-Reply-To: <1558126467.3148.9.camel@bloodnok.com> (message from Marc Munro on Fri, 17 May 2019 13:54:27 -0700)

> From: Marc Munro <marc@bloodnok.com>
> Date: Fri, 17 May 2019 13:54:27 -0700
> 
> This is a reproducible crash.  I have loaded a lot of experimental lisp
> code, including some which creates a custom header line.  It seems to
> be this that causes the crash, however only in combination with some
> buggy stuff that causes new frames to be used where a window split
> would do quite well.  
> 
> Without my window splitting bugs, I still get crashes but they are
> random and infrequent and I have been unable to create a reproducible
> test case.
> 
> I am attaching a tgz of all the files involved, and embedding a gdb
> backtrace below.
> 
> To reproduce:
> 
> $ emacs .emacs

I guess you meant

  $ emacs -l .emacs

IOW, the .emacs file should be _loaded_, not just visited.  (I tried
both, just to be sure).

> <close the *GNU Emacs* frame>

I don't have any such frame at this point.  I have a single frame
divided into 2 windows, one of them showing *GNU Emacs*, the other
showing *scratch*.

> <type M-x>

No crash here.  I tried both Emacs 26.1 and Emacs 26.2.

I'm guessing that maybe some additional files you have on your system
might be relevant.  Did you try reproducing outside your home
directory, after replacing "~marc/emacs/k" with something explicit,
and then using "emacs -q -l .emacs"?  Because this is what I did, I
cannot afford overwriting my personal .emacs file.

Can anyone else reproduce this crash?





  reply	other threads:[~2019-05-18  6: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 [this message]
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
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=83ftpc9ted.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35784@debbugs.gnu.org \
    --cc=marc@bloodnok.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).