[Cscope-devel] [ cscope-Bugs-461621 ] cscope -d aborts leaving stty in rawmode

[<no...@so...>]

Bugs item #461621, was opened at 2001-09-14 11:29
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=104664&aid=461621&group_id=4664

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Satya Nemana (satyan)
Assigned to: Hans-Bernhard Broeker (broeker)
Summary: cscope -d aborts leaving stty in rawmode

Initial Comment:
When I use 'cscope -d' option, it supposed to bring up 
the window without re-constructing the cscope.out file.

But in stead, it simply aborts with exit code 1. It 
looses the tty mode into non-echo (rawmode) which can 
be set back to normal by typing command 'stty sane'.

My test screen dump is as follows:

$ cscope -d
Cscope version 15.3       Press the ? key for help

Find this C symbol:
Find this global definition:
Find functions called by this function:
Find functions calling this function:
Find this text string:
Change this text string:
Find this egrep pattern:
Find this file:
Find files #including this file:
$
[ Now I entered 'echo $?' here, which is not visible ]
$ 1
$ [ I entered 'stty' here, which is not visible ]
$ speed 38400 baud; line = 0;
min = 1; time = 0;
-icrnl
-onlcr
-icanon -echo
[ Now I entered 'stty sane' and restored status back ]
$ stty
speed 38400 baud; line = 0;
$

I also verified this with different other cscope 
command line options such as -f -F etc. It persists.

This is not a serious bug in the sense that if you 
really want to cscope.out, you must not use this -d 
option, but on the other hand, you will end up with 
reconstructing the crooss reference file cscope.out 
everytime you invoke cscope session, which is not good.

Thanks in advance,
Satya Nemana

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2001-09-17 07:32

Message:
Logged In: NO 

Yes Broeker, it is the same CYGWIN environment that we both 
worked in past bugs. Those bugs do not appear again. I did 
removed the old cscope.out files and even then cscope -d 
exits immediately with exit code -1. I will try to debug 
further, by adding my own printfs, as I did earlier and 
email you know whatever I can find inside the execution of 
cscope.exe in source code. Thanks for your help in adv.

----------------------------------------------------------------------

Comment By: Hans-Bernhard Broeker (broeker)
Date: 2001-09-17 06:42

Message:
Logged In: YES 
user_id=27517

What platform? Cygwin again, or something else? I'll assume
the former, for now.

Aborts of cscope -d usually come from incorrect handling of
binary I/O, now (there used to be another likely cause, but
that's been taken care of, I think). So, if those are
cscope.out files from the time you had Cygwin-related
problems, reported earlier, you should make sure you
regenerate them once, with the new version, before trying -d
mode. The old ones may well be broken.



----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=104664&aid=461621&group_id=4664