Bugs item #467333, was opened at 2001-10-02 15:26
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=104664&aid=467333&group_id=4664
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Linux cscope core dumps
Initial Comment:
After compliing cscope version 15.3 in Linux version
2.0.36, cscope core dumps.
Used cscope to build database. It builds a cscope.out
file. Then if anything is searched, it core dumps.
Please help.
Attached is the core file.
----------------------------------------------------------------------
>Comment By: Petr Sorfa (petr)
Date: 2001-10-03 08:29
Message:
Logged In: YES
user_id=26835
Can you provide a little more info about which distribution
you are using and which processor.
My guess is that you are using a very old version of Linux
with possibly outdated libraries which is causing this
problem.
Also no attached core file.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=104664&aid=467333&group_id=4664

Bugs item #467333, was opened at 2001-10-02 15:26
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=104664&aid=467333&group_id=4664
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Linux cscope core dumps
Initial Comment:
After compliing cscope version 15.3 in Linux version
2.0.36, cscope core dumps.
Used cscope to build database. It builds a cscope.out
file. Then if anything is searched, it core dumps.
Please help.
Attached is the core file.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2001-10-03 14:45
Message:
Logged In: NO
Here are the answers to your questions:
Distribution: I got it from cscope.sourceforge.net.
The version is 15.3 or whatever the latest was about a
week ago.
Processor: Intel 686
Linux OS version: 2.0.36
The core file is too big to fit in your bug report max
file size. file size = 282624 bytes. MAX=256K.
----------------------------------------------------------------------
Comment By: Petr Sorfa (petr)
Date: 2001-10-03 08:29
Message:
Logged In: YES
user_id=26835
Can you provide a little more info about which distribution
you are using and which processor.
My guess is that you are using a very old version of Linux
with possibly outdated libraries which is causing this
problem.
Also no attached core file.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=104664&aid=467333&group_id=4664

Bugs item #467333, was opened at 2001-10-02 15:26
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=104664&aid=467333&group_id=4664
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Linux cscope core dumps
Initial Comment:
After compliing cscope version 15.3 in Linux version
2.0.36, cscope core dumps.
Used cscope to build database. It builds a cscope.out
file. Then if anything is searched, it core dumps.
Please help.
Attached is the core file.
----------------------------------------------------------------------
>Comment By: Hans-Bernhard Broeker (broeker)
Date: 2001-10-04 04:25
Message:
Logged In: YES
user_id=27517
You'll have to either mail the core file to one of us
personally, then, or do the analysis locally. We can help
with that.
In a nutshell:
1) make sure your cscope is compiled with debugging
information in
(a "make clean all CFLAGS='-g -O2'" should see to that,
in case of
doubt)
2) recreate the corefile. Try to parse as simple a source
file collection
as possible that still recreates the bug. The cscope
source itself
preferred
3) run
gdb cscope core
and then, from the gdb> prompt:
where
and show the output here.
A bit more information about your Linux box would also be
valuable. 2.0.36 is only the version number of the kernel
itself. The versions of GCC, the libc and maybe flex, too,
might be necessar to narrow in on this.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2001-10-03 14:45
Message:
Logged In: NO
Here are the answers to your questions:
Distribution: I got it from cscope.sourceforge.net.
The version is 15.3 or whatever the latest was about a
week ago.
Processor: Intel 686
Linux OS version: 2.0.36
The core file is too big to fit in your bug report max
file size. file size = 282624 bytes. MAX=256K.
----------------------------------------------------------------------
Comment By: Petr Sorfa (petr)
Date: 2001-10-03 08:29
Message:
Logged In: YES
user_id=26835
Can you provide a little more info about which distribution
you are using and which processor.
My guess is that you are using a very old version of Linux
with possibly outdated libraries which is causing this
problem.
Also no attached core file.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=104664&aid=467333&group_id=4664

Bugs item #467333, was opened at 2001-10-02 15:26
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=104664&aid=467333&group_id=4664
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Linux cscope core dumps
Initial Comment:
After compliing cscope version 15.3 in Linux version
2.0.36, cscope core dumps.
Used cscope to build database. It builds a cscope.out
file. Then if anything is searched, it core dumps.
Please help.
Attached is the core file.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2001-10-04 14:19
Message:
Logged In: NO
Please let me know your email address so I can
send you the core file.
The gcc version is 2.7.
libc version: 2.1.3.
flex version: 2.5.4.
I compiled the cscope as per your instructions with
-g -O2 options and redid the core file.
Following is the gdb output:
===============Begin GDB output =====================
gdb cscope core
GNU gdb 4.17.0.4 with Linux/x86 hardware watchpoint and FPU
support
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public
License, and you are
welcome to change it and/or distribute copies of it under
certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show
warranty" for details.
This GDB was configured as "i386-redhat-linux"...
Core was generated by `./cscope main.c'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libncurses.so.4...done.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
#0 0x400afd1e in old_do_write (fp=0x80935a0,
data=0x40015000 "main.c main 138 main(int argc, char
**argv)\n", to_do=44)
at oldfileops.c:294
oldfileops.c:294: No such file or directory.
(gdb) where
#0 0x400afd1e in old_do_write (fp=0x80935a0,
data=0x40015000 "main.c main 138 main(int argc, char
**argv)\n", to_do=44)
at oldfileops.c:294
#1 0x400af9a4 in _IO_old_do_write (fp=0x80935a0,
data=0x40015000 "main.c main 138 main(int argc, char
**argv)\n", to_do=44)
at oldfileops.c:267
#2 0x400afbf0 in _IO_old_file_close_it (fp=0x80935a0) at
oldfileops.c:139
#3 0x400aaf17 in freopen
(filename=0x807bc80 "/tmp/cscope10076.2",
mode=0x80607da "rb", fp=0x80935a0) at freopen.c:53
#4 0x80515e1 in search () at display.c:442
#5 0x804e91d in command (commandc=109) at command.c:504
#6 0x8057072 in main (argc=1, argv=0xbffff888) at
main.c:689
============== End gdb output ==========================
----------------------------------------------------------------------
Comment By: Hans-Bernhard Broeker (broeker)
Date: 2001-10-04 04:25
Message:
Logged In: YES
user_id=27517
You'll have to either mail the core file to one of us
personally, then, or do the analysis locally. We can help
with that.
In a nutshell:
1) make sure your cscope is compiled with debugging
information in
(a "make clean all CFLAGS='-g -O2'" should see to that,
in case of
doubt)
2) recreate the corefile. Try to parse as simple a source
file collection
as possible that still recreates the bug. The cscope
source itself
preferred
3) run
gdb cscope core
and then, from the gdb> prompt:
where
and show the output here.
A bit more information about your Linux box would also be
valuable. 2.0.36 is only the version number of the kernel
itself. The versions of GCC, the libc and maybe flex, too,
might be necessar to narrow in on this.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2001-10-03 14:45
Message:
Logged In: NO
Here are the answers to your questions:
Distribution: I got it from cscope.sourceforge.net.
The version is 15.3 or whatever the latest was about a
week ago.
Processor: Intel 686
Linux OS version: 2.0.36
The core file is too big to fit in your bug report max
file size. file size = 282624 bytes. MAX=256K.
----------------------------------------------------------------------
Comment By: Petr Sorfa (petr)
Date: 2001-10-03 08:29
Message:
Logged In: YES
user_id=26835
Can you provide a little more info about which distribution
you are using and which processor.
My guess is that you are using a very old version of Linux
with possibly outdated libraries which is causing this
problem.
Also no attached core file.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=104664&aid=467333&group_id=4664

Bugs item #467333, was opened at 2001-10-02 15:26
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=104664&aid=467333&group_id=4664
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Hans-Bernhard Broeker (broeker)
Summary: Linux cscope core dumps
Initial Comment:
After compliing cscope version 15.3 in Linux version
2.0.36, cscope core dumps.
Used cscope to build database. It builds a cscope.out
file. Then if anything is searched, it core dumps.
Please help.
Attached is the core file.
----------------------------------------------------------------------
>Comment By: Hans-Bernhard Broeker (broeker)
Date: 2001-10-05 06:06
Message:
Logged In: YES
user_id=27517
< my username> @ sourceforge.net works as a mail address.
The corefile alone would hardly be useful, anyway: I'ld need
the executable, too.
Regarding the gdb session dump, the problem it shows is
rather hard to analyze. The segfault happens inside a libc
function. Setting aside possible bugs in your (relatively
old) libc, the typical reasons for this would be heap
corruption having happened earlier on, which just happen to
trigger a problem now. To debug one of those, you typically
need special tools, like a debugging malloc() and/or
the Electric Fence library (--> man libefence).
As another check, please see if
./cscope -lL0main main.c
also crashes. If it doesn't, the culprit might be your
curses library.
In that case, the "configure" generated files (config.h,
config.cache, config.log) would be useful for seeing what
may have gone wrong in detecting them.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2001-10-04 14:19
Message:
Logged In: NO
Please let me know your email address so I can
send you the core file.
The gcc version is 2.7.
libc version: 2.1.3.
flex version: 2.5.4.
I compiled the cscope as per your instructions with
-g -O2 options and redid the core file.
Following is the gdb output:
===============Begin GDB output =====================
gdb cscope core
GNU gdb 4.17.0.4 with Linux/x86 hardware watchpoint and FPU
support
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public
License, and you are
welcome to change it and/or distribute copies of it under
certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show
warranty" for details.
This GDB was configured as "i386-redhat-linux"...
Core was generated by `./cscope main.c'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libncurses.so.4...done.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
#0 0x400afd1e in old_do_write (fp=0x80935a0,
data=0x40015000 "main.c main 138 main(int argc, char
**argv)\n", to_do=44)
at oldfileops.c:294
oldfileops.c:294: No such file or directory.
(gdb) where
#0 0x400afd1e in old_do_write (fp=0x80935a0,
data=0x40015000 "main.c main 138 main(int argc, char
**argv)\n", to_do=44)
at oldfileops.c:294
#1 0x400af9a4 in _IO_old_do_write (fp=0x80935a0,
data=0x40015000 "main.c main 138 main(int argc, char
**argv)\n", to_do=44)
at oldfileops.c:267
#2 0x400afbf0 in _IO_old_file_close_it (fp=0x80935a0) at
oldfileops.c:139
#3 0x400aaf17 in freopen
(filename=0x807bc80 "/tmp/cscope10076.2",
mode=0x80607da "rb", fp=0x80935a0) at freopen.c:53
#4 0x80515e1 in search () at display.c:442
#5 0x804e91d in command (commandc=109) at command.c:504
#6 0x8057072 in main (argc=1, argv=0xbffff888) at
main.c:689
============== End gdb output ==========================
----------------------------------------------------------------------
Comment By: Hans-Bernhard Broeker (broeker)
Date: 2001-10-04 04:25
Message:
Logged In: YES
user_id=27517
You'll have to either mail the core file to one of us
personally, then, or do the analysis locally. We can help
with that.
In a nutshell:
1) make sure your cscope is compiled with debugging
information in
(a "make clean all CFLAGS='-g -O2'" should see to that,
in case of
doubt)
2) recreate the corefile. Try to parse as simple a source
file collection
as possible that still recreates the bug. The cscope
source itself
preferred
3) run
gdb cscope core
and then, from the gdb> prompt:
where
and show the output here.
A bit more information about your Linux box would also be
valuable. 2.0.36 is only the version number of the kernel
itself. The versions of GCC, the libc and maybe flex, too,
might be necessar to narrow in on this.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2001-10-03 14:45
Message:
Logged In: NO
Here are the answers to your questions:
Distribution: I got it from cscope.sourceforge.net.
The version is 15.3 or whatever the latest was about a
week ago.
Processor: Intel 686
Linux OS version: 2.0.36
The core file is too big to fit in your bug report max
file size. file size = 282624 bytes. MAX=256K.
----------------------------------------------------------------------
Comment By: Petr Sorfa (petr)
Date: 2001-10-03 08:29
Message:
Logged In: YES
user_id=26835
Can you provide a little more info about which distribution
you are using and which processor.
My guess is that you are using a very old version of Linux
with possibly outdated libraries which is causing this
problem.
Also no attached core file.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=104664&aid=467333&group_id=4664

Bugs item #467333, was opened at 2001-10-02 15:26
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=104664&aid=467333&group_id=4664
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Hans-Bernhard Broeker (broeker)
Summary: Linux cscope core dumps
Initial Comment:
After compliing cscope version 15.3 in Linux version
2.0.36, cscope core dumps.
Used cscope to build database. It builds a cscope.out
file. Then if anything is searched, it core dumps.
Please help.
Attached is the core file.
----------------------------------------------------------------------
>Comment By: Hans-Bernhard Broeker (broeker)
Date: 2001-10-05 06:07
Message:
Logged In: YES
user_id=27517
Ooops, a little correction, regarding the mail address: make
that
@users.sourceforge.net
----------------------------------------------------------------------
Comment By: Hans-Bernhard Broeker (broeker)
Date: 2001-10-05 06:06
Message:
Logged In: YES
user_id=27517
< my username> @ sourceforge.net works as a mail address.
The corefile alone would hardly be useful, anyway: I'ld need
the executable, too.
Regarding the gdb session dump, the problem it shows is
rather hard to analyze. The segfault happens inside a libc
function. Setting aside possible bugs in your (relatively
old) libc, the typical reasons for this would be heap
corruption having happened earlier on, which just happen to
trigger a problem now. To debug one of those, you typically
need special tools, like a debugging malloc() and/or
the Electric Fence library (--> man libefence).
As another check, please see if
./cscope -lL0main main.c
also crashes. If it doesn't, the culprit might be your
curses library.
In that case, the "configure" generated files (config.h,
config.cache, config.log) would be useful for seeing what
may have gone wrong in detecting them.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2001-10-04 14:19
Message:
Logged In: NO
Please let me know your email address so I can
send you the core file.
The gcc version is 2.7.
libc version: 2.1.3.
flex version: 2.5.4.
I compiled the cscope as per your instructions with
-g -O2 options and redid the core file.
Following is the gdb output:
===============Begin GDB output =====================
gdb cscope core
GNU gdb 4.17.0.4 with Linux/x86 hardware watchpoint and FPU
support
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public
License, and you are
welcome to change it and/or distribute copies of it under
certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show
warranty" for details.
This GDB was configured as "i386-redhat-linux"...
Core was generated by `./cscope main.c'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libncurses.so.4...done.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
#0 0x400afd1e in old_do_write (fp=0x80935a0,
data=0x40015000 "main.c main 138 main(int argc, char
**argv)\n", to_do=44)
at oldfileops.c:294
oldfileops.c:294: No such file or directory.
(gdb) where
#0 0x400afd1e in old_do_write (fp=0x80935a0,
data=0x40015000 "main.c main 138 main(int argc, char
**argv)\n", to_do=44)
at oldfileops.c:294
#1 0x400af9a4 in _IO_old_do_write (fp=0x80935a0,
data=0x40015000 "main.c main 138 main(int argc, char
**argv)\n", to_do=44)
at oldfileops.c:267
#2 0x400afbf0 in _IO_old_file_close_it (fp=0x80935a0) at
oldfileops.c:139
#3 0x400aaf17 in freopen
(filename=0x807bc80 "/tmp/cscope10076.2",
mode=0x80607da "rb", fp=0x80935a0) at freopen.c:53
#4 0x80515e1 in search () at display.c:442
#5 0x804e91d in command (commandc=109) at command.c:504
#6 0x8057072 in main (argc=1, argv=0xbffff888) at
main.c:689
============== End gdb output ==========================
----------------------------------------------------------------------
Comment By: Hans-Bernhard Broeker (broeker)
Date: 2001-10-04 04:25
Message:
Logged In: YES
user_id=27517
You'll have to either mail the core file to one of us
personally, then, or do the analysis locally. We can help
with that.
In a nutshell:
1) make sure your cscope is compiled with debugging
information in
(a "make clean all CFLAGS='-g -O2'" should see to that,
in case of
doubt)
2) recreate the corefile. Try to parse as simple a source
file collection
as possible that still recreates the bug. The cscope
source itself
preferred
3) run
gdb cscope core
and then, from the gdb> prompt:
where
and show the output here.
A bit more information about your Linux box would also be
valuable. 2.0.36 is only the version number of the kernel
itself. The versions of GCC, the libc and maybe flex, too,
might be necessar to narrow in on this.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2001-10-03 14:45
Message:
Logged In: NO
Here are the answers to your questions:
Distribution: I got it from cscope.sourceforge.net.
The version is 15.3 or whatever the latest was about a
week ago.
Processor: Intel 686
Linux OS version: 2.0.36
The core file is too big to fit in your bug report max
file size. file size = 282624 bytes. MAX=256K.
----------------------------------------------------------------------
Comment By: Petr Sorfa (petr)
Date: 2001-10-03 08:29
Message:
Logged In: YES
user_id=26835
Can you provide a little more info about which distribution
you are using and which processor.
My guess is that you are using a very old version of Linux
with possibly outdated libraries which is causing this
problem.
Also no attached core file.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=104664&aid=467333&group_id=4664

Bugs item #467333, was opened at 2001-10-02 15:26
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=104664&aid=467333&group_id=4664
Category: None
Group: None
>Status: Closed
>Resolution: Works For Me
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Hans-Bernhard Broeker (broeker)
Summary: Linux cscope core dumps
Initial Comment:
After compliing cscope version 15.3 in Linux version
2.0.36, cscope core dumps.
Used cscope to build database. It builds a cscope.out
file. Then if anything is searched, it core dumps.
Please help.
Attached is the core file.
----------------------------------------------------------------------
>Comment By: Hans-Bernhard Broeker (broeker)
Date: 2001-10-15 03:28
Message:
Logged In: YES
user_id=27517
After a longish private email exchange, we found the bugger:
it appears to be an outright buggy implementation of
freopen() hiding in the particular version of glibc he used.
For reference: both very old and reasonably current versions
of Linux libc get this right --- only some medium-old ones
contain this bug, it seems.
----------------------------------------------------------------------
Comment By: Hans-Bernhard Broeker (broeker)
Date: 2001-10-05 06:07
Message:
Logged In: YES
user_id=27517
Ooops, a little correction, regarding the mail address: make
that
@users.sourceforge.net
----------------------------------------------------------------------
Comment By: Hans-Bernhard Broeker (broeker)
Date: 2001-10-05 06:06
Message:
Logged In: YES
user_id=27517
< my username> @ sourceforge.net works as a mail address.
The corefile alone would hardly be useful, anyway: I'ld need
the executable, too.
Regarding the gdb session dump, the problem it shows is
rather hard to analyze. The segfault happens inside a libc
function. Setting aside possible bugs in your (relatively
old) libc, the typical reasons for this would be heap
corruption having happened earlier on, which just happen to
trigger a problem now. To debug one of those, you typically
need special tools, like a debugging malloc() and/or
the Electric Fence library (--> man libefence).
As another check, please see if
./cscope -lL0main main.c
also crashes. If it doesn't, the culprit might be your
curses library.
In that case, the "configure" generated files (config.h,
config.cache, config.log) would be useful for seeing what
may have gone wrong in detecting them.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2001-10-04 14:19
Message:
Logged In: NO
Please let me know your email address so I can
send you the core file.
The gcc version is 2.7.
libc version: 2.1.3.
flex version: 2.5.4.
I compiled the cscope as per your instructions with
-g -O2 options and redid the core file.
Following is the gdb output:
===============Begin GDB output =====================
gdb cscope core
GNU gdb 4.17.0.4 with Linux/x86 hardware watchpoint and FPU
support
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public
License, and you are
welcome to change it and/or distribute copies of it under
certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show
warranty" for details.
This GDB was configured as "i386-redhat-linux"...
Core was generated by `./cscope main.c'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libncurses.so.4...done.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
#0 0x400afd1e in old_do_write (fp=0x80935a0,
data=0x40015000 "main.c main 138 main(int argc, char
**argv)\n", to_do=44)
at oldfileops.c:294
oldfileops.c:294: No such file or directory.
(gdb) where
#0 0x400afd1e in old_do_write (fp=0x80935a0,
data=0x40015000 "main.c main 138 main(int argc, char
**argv)\n", to_do=44)
at oldfileops.c:294
#1 0x400af9a4 in _IO_old_do_write (fp=0x80935a0,
data=0x40015000 "main.c main 138 main(int argc, char
**argv)\n", to_do=44)
at oldfileops.c:267
#2 0x400afbf0 in _IO_old_file_close_it (fp=0x80935a0) at
oldfileops.c:139
#3 0x400aaf17 in freopen
(filename=0x807bc80 "/tmp/cscope10076.2",
mode=0x80607da "rb", fp=0x80935a0) at freopen.c:53
#4 0x80515e1 in search () at display.c:442
#5 0x804e91d in command (commandc=109) at command.c:504
#6 0x8057072 in main (argc=1, argv=0xbffff888) at
main.c:689
============== End gdb output ==========================
----------------------------------------------------------------------
Comment By: Hans-Bernhard Broeker (broeker)
Date: 2001-10-04 04:25
Message:
Logged In: YES
user_id=27517
You'll have to either mail the core file to one of us
personally, then, or do the analysis locally. We can help
with that.
In a nutshell:
1) make sure your cscope is compiled with debugging
information in
(a "make clean all CFLAGS='-g -O2'" should see to that,
in case of
doubt)
2) recreate the corefile. Try to parse as simple a source
file collection
as possible that still recreates the bug. The cscope
source itself
preferred
3) run
gdb cscope core
and then, from the gdb> prompt:
where
and show the output here.
A bit more information about your Linux box would also be
valuable. 2.0.36 is only the version number of the kernel
itself. The versions of GCC, the libc and maybe flex, too,
might be necessar to narrow in on this.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2001-10-03 14:45
Message:
Logged In: NO
Here are the answers to your questions:
Distribution: I got it from cscope.sourceforge.net.
The version is 15.3 or whatever the latest was about a
week ago.
Processor: Intel 686
Linux OS version: 2.0.36
The core file is too big to fit in your bug report max
file size. file size = 282624 bytes. MAX=256K.
----------------------------------------------------------------------
Comment By: Petr Sorfa (petr)
Date: 2001-10-03 08:29
Message:
Logged In: YES
user_id=26835
Can you provide a little more info about which distribution
you are using and which processor.
My guess is that you are using a very old version of Linux
with possibly outdated libraries which is causing this
problem.
Also no attached core file.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=104664&aid=467333&group_id=4664