unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 56967@debbugs.gnu.org, bjorn.bidar@thaodan.de
Subject: bug#56967: 29.0.50; Frequent crashes under Wayland
Date: Fri, 05 Aug 2022 09:43:44 +0300	[thread overview]
Message-ID: <83mtcj197j.fsf@gnu.org> (raw)
In-Reply-To: <87les39pbu.fsf@yahoo.com> (message from Po Lu on Fri, 05 Aug 2022 14:28:21 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: bjorn.bidar@thaodan.de,  56967@debbugs.gnu.org
> Date: Fri, 05 Aug 2022 14:28:21 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Does _exit in glibc provide any hooks that we could use?
> 
> Not that I know of.

How about asking the glibc developers to provide one, citing this very
use case as the real-life problem to solve?  Specifically, what I'd
like to do in that hook is to shut down Emacs in an orderly manner, so
that the user won't lose all his/her edits.

> > Or maybe GTK has some knob to let it call us before it calls _exit?
> 
> Nope, GTK simply does this:
> 
>   if (wl_display_flush (display->wl_display) < 0)
>     {
>       g_message ("Error flushing display: %s", g_strerror (errno));
>       _exit (1);
>     }
> 
> if (for example) wl_display_flush, a low-level Wayland interface, fails
> from an IO error.

Amazing.  Where did those people learn to develop friendly, extensible
libraries? in what tyrannical culture?





  reply	other threads:[~2022-08-05  6:43 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04  7:36 bug#56967: 29.0.50; Frequent crashes under Wayland Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04  8:01 ` Eli Zaretskii
     [not found]   ` <3230275.qDoO4GC8Cx@odin>
2022-08-04  8:21     ` Eli Zaretskii
2022-08-04 11:49       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05  0:18         ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05  0:50           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05  6:25             ` Eli Zaretskii
2022-08-05  6:28               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05  6:43                 ` Eli Zaretskii [this message]
2022-08-05  6:53                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05  7:46                     ` Eli Zaretskii
2022-08-05  8:26                       ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05  8:38                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05  6:56                 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05  6:59                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 11:40               ` Gregory Heytings
2022-08-05 11:50                 ` Eli Zaretskii
     [not found]             ` <2972937.jrzt3BHeHG@odin>
2022-08-05  6:29               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 14:51                 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 15:07                   ` Eli Zaretskii
2022-08-07 15:14                     ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 15:44                       ` Eli Zaretskii
2022-08-08  2:42                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-08  2:40                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-08  6:07                     ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-08  8:56                     ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-08 10:10                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-13 12:10                       ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-13 12:10                       ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-13 13:11                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-13 17:06                           ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05  6:31             ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]             ` <2189728.upBv5HjrgE@odin>
2022-08-05  6:31               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]             ` <1917872.q2Y8mqo1ke@odin>
2022-08-05  6:35               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05  6:55                 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05  7:01                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-17 16:02 ` Gavin Massingham
     [not found] <CAH3b6=SPM_Pys81fi-_Eu=VXO8mETqV+s0YFC+8c1huv4dmh9Q@mail.gmail.com>
2022-08-04 18:29 ` Eli Zaretskii
2022-08-05  7:34   ` 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=83mtcj197j.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=56967@debbugs.gnu.org \
    --cc=bjorn.bidar@thaodan.de \
    --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).