From: martin rudalics <rudalics@gmx.at>
To: Levi <wacossusca34@gmail.com>, 28862@debbugs.gnu.org
Subject: bug#28862: Emacs 25.3.1 segmentation fault on killing *Colors* buffer
Date: Wed, 18 Oct 2017 10:12:07 +0200 [thread overview]
Message-ID: <59E70CD7.3010700@gmx.at> (raw)
In-Reply-To: <CAM1nYoHo5UcE+vA1-gHjXbzXYBOwkoV9bk8Gcdv2of3-d1SxeA@mail.gmail.com>
> Have you (or anyone else) been able to reproduce the issue? If not, I can
> start looking at other potential factors on my system.
I was not able to reproduce it. But I do not understand some parts of
your scenario:
> 1) Run `emacs -Q` in a terminal with an X server running, spawning the X
> frontend for emacs
Is 1) strictly necessary?
> 2) Paste the above code into the *scratch* buffer and evaluate it (with
> `M-x eval-buffer`).
>
> 3) Spawn a new frame (with `C-x 5 2`)
>
> 4) Enter the customization menus (with `M-x customize`)
>
> 5) Navigate to any face in the UI, for example `Emacs -> Faces -> Basic
> Faces -> Cursor face`
>
> 6) Expand the options for the face of interest and click on `Choose` for a
> color. The colors buffer should appear in a new window, splitting the frame
> in half.
>
> 7) Close the window containing the *Customize Group: ...*, such that the
> only buffer visible in the frame is the *Colors* buffer (I do this by
> right-clicking the modeline)
Can't you instead of 4)-7) simply run ‘list-colors-display’?
> 8) Close the frame via the window manager (`X` button, or some hotkey to
> close the X window).
Does C-x 5 0 not exhibit the bug?
In any case please use GDB to step through delete_frame. If it survives
‘delete-frame-functions’ it should be easy to see where it crashes.
martin
next prev parent reply other threads:[~2017-10-18 8:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 2:49 bug#28862: Emacs 25.3.1 segmentation fault on killing *Colors* buffer Levi
2017-10-16 8:16 ` martin rudalics
2017-10-16 15:10 ` Eli Zaretskii
2017-10-17 2:30 ` Levi
2017-10-17 8:59 ` martin rudalics
2017-10-17 23:14 ` Levi
2017-10-18 8:12 ` martin rudalics [this message]
2017-11-01 23:08 ` Noam Postavsky
2019-06-30 4:48 ` Stefan Kangas
2019-08-23 6:27 ` Stefan Kangas
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=59E70CD7.3010700@gmx.at \
--to=rudalics@gmx.at \
--cc=28862@debbugs.gnu.org \
--cc=wacossusca34@gmail.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).