[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: O_STATIC implies 'special' justification, is this really necessary?
From: |
Thomas Dickey |
Subject: |
Re: O_STATIC implies 'special' justification, is this really necessary? |
Date: |
Sat, 8 Oct 2005 16:22:02 -0400 |
User-agent: |
Mutt/1.5.9i |
On Sat, Oct 01, 2005 at 04:48:26PM -0400, Thomas Dickey wrote:
...
> A quick check on Solaris setting O_STATIC off makes demo_forms (using its -d
> option) dump core with at the
>
> field_opts_off(f, O_STATIC);
>
> so I can't see the visual effect (if any) for comparison.
I can see why the core dump happens - a bug in Solaris curses. By reading
http://cvs.opensolaris.org/source/xref/usr/src/lib/libeti/form/common/utility.c#_sync_opts
The _sync_opts() function has some contradictory logic: it checks if
f->form
isn't null via the Connected() macro, and does some work based on that
in the first chunk. But down in the second chunk, it uses f->form
without checking, to get the form's status (f->form->status) in the
Posted() macro.
So it is not possible to use field_opts_off() with Solaris curses until
after the form has been posted. I'll ifdef that in demo_forms.c and
note the problem there.
--
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net
signature.asc
Description: Digital signature