On Mon, Sep 16, 2002 at 06:18:32PM -0700, Umar Qureshey wrote:
> Ok here's big clue (I think): Instead of launching my ncurses-based app, I
> launched the ncurses.c test program and that seems to be working fine. So,
> this means that whatever problem there is, it is internal to my app. Does
> this make sense?
Lynx could simply be using too much memory. Try turning this option off:
-curses_pads uses curses pad feature to support left/right shifting (on)
If it's not so simple, my approach would be to see if
a) just the size of lynx + subprogram is a factor anyway (by modifying
lynx to immediately spawn a subprogram from different points in
the initialization)
b) add some logic to the subprogram to check if stdout is closed, if
it is able to write some sort of trace-file to show its state.
--
Thomas E. Dickey <[EMAIL PROTECTED]>
http://invisible-island.net
ftp://invisible-island.net
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
