unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Antonio Carzaniga <antonio.carzaniga@usi.ch>
Cc: 53420@debbugs.gnu.org
Subject: bug#53420: 29.0.50; NULL cairo context while frame resize, causes segfault with visible-bell
Date: Sat, 22 Jan 2022 09:13:20 +0800	[thread overview]
Message-ID: <87ilucwp1r.fsf@yahoo.com> (raw)
In-Reply-To: <877dateyyi.fsf@usi.ch> (Antonio Carzaniga's message of "Fri, 21 Jan 2022 16:49:25 +0100")

Antonio Carzaniga <antonio.carzaniga@usi.ch> writes:

> M-x set-variable RET visible-bell
>
> Now resize the emacs frame and at the same time give a keyboard command
> that causes emacs to ring the bell.  I know it's not a common thing to
> do, in fact I just happened to do that by mistake.  Specifically for me,
> s-<up> maximizes the frame vertically, and I also pressed <down>, which
> causes emacs to complain that s-<down> is undefined and therefore ring
> the bell.
>
> Anyway, now emacs crashes.  A bit of analysis reveals the following
> sequence of events (logged using gdb) in which the cairo context
> associated with the selected frame is temporarily set to null during the
> frame-resize operation, and pgtk_ring_bell and then pgtk_flash are
> called before the cairo context is properly restored.

Thanks, should be fixed now.





  reply	other threads:[~2022-01-22  1:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 15:49 bug#53420: 29.0.50; NULL cairo context while frame resize, causes segfault with visible-bell Antonio Carzaniga
2022-01-22  1:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-22 21:07   ` Antonio Carzaniga
2022-01-23  0:44     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23 17:34       ` Antonio Carzaniga
2022-01-24  0:04         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87ilucwp1r.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53420@debbugs.gnu.org \
    --cc=antonio.carzaniga@usi.ch \
    --cc=luangruo@yahoo.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).