next message in archive
next message in thread
previous message in archive
Index of Subjects
On Mon, 29 May 2000, Daniele Fornacia wrote:
> thank for your help!
Lynx died during curses (terminal I/O) startup:
(gdb) info sharedlibrary
From To Syms Read Shared Object Library
0x40018000 0x00000000 No /lib/libncurses.so.4
0x4005a000 0x4014c8dc Yes /lib/libc.so.6
0x40000000 0x400126b0 Yes /lib/ld-linux.so.2
0x4015c000 0x401649a0 Yes /lib/libnss_files.so.2
0x40158000 0x40159ac0 Yes /usr/lib/gconv/ISO8859-1.so
(gdb) add-symbol-file /usr/lib/libncurses.so.4 0x40018000
(gdb) bt
#0 0x400784e1 in __kill () from /lib/libc.so.6
#1 0x40078156 in raise (sig=6) at ../sysdeps/posix/raise.c:27
#2 0x40079868 in abort () at ../sysdeps/generic/abort.c:88
#3 0x8060978 in FatalProblem ()
#4 0x40078408 in __restore ()
at ../sysdeps/unix/sysv/linux/i386/sigaction.c:127
#5 0x40035f2b in table.73 ()
#6 0x400361f7 in table.73 ()
#7 0x40033dad in postprocess_termcap ()
#8 0x4003107a in tparm ()
#9 0x806bd81 in start_curses ()
#10 0x806bffc in setup ()
#11 0x805ec0b in main ()
#12 0x400721eb in __libc_start_main (main=0x805cfe0 <main>, argc=4,
argv=0xbffff854, init=0x8049eb8 <_init>, fini=0x80d890c <_fini>,
rtld_fini=0x4000a610 <_dl_fini>, stack_end=0xbffff84c)
at ../sysdeps/generic/libc-start.c:90
What version of ncurses do you have installed? On my Red Hat 6.1 system,
`rpm -qa|grep curses' gives me this:
ncurses3-1.9.9e-9
ncurses-devel-4.2-22
ncurses-4.2-22
ncurses-4.2-22 is what Lynx is linked against. The binary you sent works
on my system.
Oddly enough there only seem to have been four environment variables set
when the binary started up:
HOME=/root
USER=root
CS_ROOT=/opt/csuite
DOCUMENT_ROOT=/opt/csuite/info
The csbuild2 script should have set many more. Could you add two lines
env > env2.out
set > set2.out
to the end of the csbuild2 script, rerun the install process, and send me
env2.out & set2.out?
BTW, you mailed me lynx.cfg.build, not lynx.cfg. lynx.cfg is generated
from lynx.cfg.build. I don't think it makes any difference, but there's
always a possibility one of the substituted config settings is somehow
causing problems.
next message in archive
next message in thread
previous message in archive
Index of Subjects