Re: Strange behavior of Ncurses

[Thomas Dickey]

On Fri, Oct 18, 2024 at 03:43:10PM -0400, Thomas Dickey wrote:
> time permitting, I'll construct a program from the traces and see if there's
> some improvement that I might make to the optimization (or some recommendation
> or changes to the terminal description which would address this device).

taking a quick look, however, there's something amiss with those traces.

This chunk at 4% through the trace shows wgetch being called and not
returning.  Instead it's showing wprintw called (and lacking the return
from wgetch) nested down another level:

Update cost: 2 chars, 0 clocks system time, 0 clocks user time
+ + called {_nc_signal_handler(1)
+ + return }
+ return }0
return }0
called {wgetch(0x18000d0)
+ called {_nc_wgetch(0x18000d0)
+ + called {is_wintouched(0x18000d0)
+ + return }0
kgetch() called
+ + called {wprintw(0x18000d0,"%s", "SCCP POLICING SPECIFICATION DATA")
+ + + called {vwprintw(0x18000d0,"%s",va_list)
+ + + + called {waddnstr(0x18000d0,"SCCP POLICING SPECIFICATION DATA",-1)
... current {A_NORMAL}

That won't happen with ncurses 6.1, unless

a) the trace is incomplete, -- but both traces have the same quirk, or

b) ncurses was modified in some manner -- but earlier wgetch calls return, or

c) ncurses is being used in some unexpected manner, e.g., in a multithreaded
   application.  Doing that will introduce lots of anomalies :-)

-- 
Thomas E. Dickey <dickey@invisible-island.net>
https://invisible-island.net

signature.asc
Description: PGP signature