[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#65193: 29.1.50; SET_FRAME_ICONIFIED can cause Lisp evaluation inside
From: |
Eli Zaretskii |
Subject: |
bug#65193: 29.1.50; SET_FRAME_ICONIFIED can cause Lisp evaluation inside read_socket_hook. |
Date: |
Sat, 12 Aug 2023 10:30:40 +0300 |
> Date: Fri, 11 Aug 2023 08:29:30 +0900
> From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
> Cc: luangruo@yahoo.com,
> 65193@debbugs.gnu.org
>
> On Fri, 11 Aug 2023 02:58:50 +0900,
> Eli Zaretskii wrote:
> >
> > > Cc: 65193@debbugs.gnu.org
> > > Date: Fri, 11 Aug 2023 01:33:41 +0900
> > > From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
> > >
> > > Another problem specific to the NS port w.r.t. the call to
> > > gui_consider_frame_title from SET_FRAME_ICONIFIED is that it can
> > > also be called inside the select emulation via -[EmacsView
> > > windowDidDeminiaturize:] for example.
> >
> > Please describe in more detail how such a call could happen, including
> > the sequence of calls which could call SET_FRAME_ICONIFIED from the
> > select emulation. This situation, if it can happen, should be
> > investigated.
>
> Sorry, I thought the NS port can run another Lisp thread while one
> thread is waiting for inputs with (emulated) select as in other
> platforms (including the Mac port). But actually that's not the case,
> so the situation I said does not happen with the current NS select
> emulation. Of course, once the NS port obtains such ability, the
> problem I described will happen.
>
> Below is the stacktrace that leads to SET_FRAME_ICONIFIED from the NS
> select emulation (ns_select):
OK, thanks.