On 12/4/16 7:42 PM, Hong Cho wrote:
>
> The race condition is that “history_length” gets updated before the
> “the_history” update is completed.
>
>
>
> In several cases we’ve encountered, “bash” got a signal (SIGHUP), which
> interrupted add_history(), leaving “the_history” and “history_length”
> inconsistent. In the signal handling path, it tried to access “the_history”
> in history_do_write() in histfile.c, which tried to de-reference a NULL
> pointer.
Thanks for the report. This looks like a good fix.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
