Red Hat Bugzilla – Bug 105999
LTC4630-cscope SEGVs in ncurses in RHEL3 beta2 on x86_64
Last modified: 2007-11-30 17:06:58 EST
The following has be reported by IBM LTC:
cscope SEGVs in ncurses in RHEL3 beta2 on x86_64
RHEL 3.0 beta2 for x86_64
Steps to Reproduce:
1. d/l cscope-15.5.tar.gz from cscope.sourceforge.net, unpack.
2. ./configure; make (build completes successfully)
Program received signal SIGSEGV, Segmentation fault.
0x0000002a958419b0 in strlen () from /lib64/tls/libc.so.6
#0 0x0000002a958419b0 in strlen () from /lib64/tls/libc.so.6
#1 0x0000002a958106fe in vfprintf () from /lib64/tls/libc.so.6
#2 0x0000002a9582e505 in vsprintf () from /lib64/tls/libc.so.6
#3 0x0000002a95698555 in _nc_printf_string (
fmt=0x449128 "Cscope version %d%s", ap=0x7fbffff110)
#4 0x0000002a956940c1 in vwprintw (win=0x575db8,
fmt=0x20 <Address 0x20 out of bounds>, argp=0x2a95812220)
#5 0x0000002a95693e6a in printw (fmt=0x20 <Address 0x20 out of bounds>)
#6 0x000000000040bb84 in display () at display.c:161
#7 0x0000000000411bca in main (argc=0, argv=0x7fbffff808) at main.c:385
cscope-15.4 built and ran fine on SLES8 for x86_64 (built from
configure in cscope-15.4 doesn't x86_64 architecture:
checking build system type... Invalid configuration `x86_64-unknown-linux-gnu':
machine `x86_64-unknown' not recognized
configure: error: /bin/sh ./config.sub x86_64-unknown-linux-gnu failed.
SLES8 is no longer available on x86_64, so there's no way to check if
cscope-15.5 would have worked. From the stack traceback it looks like the real
bug is in ncurses lib though, so cscope version may not be very relevant.
BTW, someone needs to add x86_64 (or AMD64, whatever's the official name now)
to bugzilla arch list.Glen/Greg - please submit this to Red Hat. This is a
RHEL3 beta2 problem
on x86-64 (AMD64) platform (Opteron). Thanks.
------ Additional Comments From email@example.com 2003-02-10 14:27 -------
This got fixed in RC2.
the configure --enable-safe-sprintf problem huh? Understood. Closing.
*** This bug has been marked as a duplicate of 103790 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.