Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000131OCamlOCaml generalpublic2000-06-06 15:292000-06-06 15:51
Reporteradministrator 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0000131: threads, terminals & bash
DescriptionHello,

some months ago (November last year) you fixed a bug concerning the setting
of non-blocking mode on standard channels that messed up the terminal on my
machine (a Sparc running Solaris).

You had mentioned that there might still be problems if the program gets a
(deadly) signal, in which case it will not necessarily terminate leaving a
"sane" terminal state.

I kept indeed experiencing problems from time to time, but only now got
annoyed enough to look into it:

Now, it seems that it is really rather a bash bug that causes my grief. It
should actually be the duty of the shell to guarantee that the terminal is
restored to a sane state after the termination of programs, but our version
(bash-2.00.0(1) - a very (?) encouraging version number) obviously did not
do this.

In case anybode else complains about "vanishing lines", CPU-eating bash
sessions and whatever, I recommend taking a look at the version of the
shell and upgrading to a new one if necessary (bash-2.04 works fine).

I just wanted to tell you so that you do not look for problems in your
sources if it is another program which is the cause of the bug...

Best regards,
Markus

--
Markus Mottl, mottl@miss.wu-wien.ac.at, http://miss.wu-wien.ac.at/~mottl [^]

TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0002118)
administrator (administrator)
2000-06-06 15:51

Summary: upgrading bash helps

- Issue History
Date Modified Username Field Change
2005-11-18 10:13 administrator New Issue


Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker