This was reported to upstream:
An user reported a problem, that apparently happens for quite
The user reports that interrupting this command:
eval sleep 10
would keep history in tcsh-6.14.00, but not in tcsh-6.18.01.
Actually, I believe the history not being logged is due to
and the problem is another, as the inconsistent state
happens in all tcsh versions. Basically, when doeval()
calls process(), process() does not leave, so one needs
to ^D twice to get back to the consistent state.
The attached patch correct this condition, and based
on code I could read is correct, but I would like some
feedback on it.
Created attachment 1023589 [details]
Created attachment 1023775 [details]
Update patch, as initially proposed patch would
break the shell (was exiting if pressing ^C),
while the idea was to just leave the inconsistent
state after ^C during eval.
Thanks for the report and provided patch!
It looks OK to me and it sounds reasonable to merge this patch, no fail noted in upstream testsuite as well.
Here is the mailing list conversation mentioned in the comment #0:
The conversation in the mailing list might be misleading to somebody - it might look like the patch was not accepted:
> And removed. This breaks the shell completely; a ^C makes it exit.
However, will small tweak, the patch was accepted by the upstream:
(In reply to Paulo Andrade from comment #0)
> The user reports that interrupting this command:
> eval sleep 10
> would keep history in tcsh-6.14.00, but not in tcsh-6.18.01.
This actually does not aplly for the RHEL-6, since we use a different source base (tcsh-6.17.00).
It might apply for the RHEL-7, but I'm not able to acquire a testing machine at the moment. I will try to test it tomorrow and if I see any ~/.history file corruption, I would create a separate BZ for it.
Regarding this part:
> and the problem is another, as the inconsistent state
> happens in all tcsh versions. Basically, when doeval()
> calls process(), process() does not leave, so one needs
> to ^D twice to get back to the consistent state.
I have applied the patch and it should be part of the errata for RHEL-6.8.
I'm sorry, but I was not able to reproduce the ~/.history file corruption on RHEL-7 machine either (tcsh-6.18.01-8.el7.x86_64).
Therefore, unless you or somebody else provide us with info how to reproduce the ~/.history file corruption, we can't help you with that matter. If that matter persists for you, feel free to create a separate BZ for it.
Thank you for your understanding.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.