[asterisk-bugs] [Asterisk 0016858]: asterisk command history loads as unusable garbage

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16858 
====================================================================== 
Reported By:                jw-asterisk
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16858
Category:                   Core/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.2.2 
JIRA:                       SWP-932 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-17 21:19 CST
Last Modified:              2010-03-03 20:13 CST
====================================================================== 
Summary:                    asterisk command history loads as unusable garbage
Description: 
When using asterisk interactively with command interface a history file is
created (~/.asterisk_history). Lines written to the history file are
white-space encoded (in ast_el_write_history:history:case
H_SAVE:history_save:strvis).

But when the history file is loaded it reverse (strunvis) is not
performed.  Therefore the history becomes unusable garbage.
====================================================================== 

---------------------------------------------------------------------- 
 (0118933) jw-asterisk (reporter) - 2010-03-03 20:13
 https://issues.asterisk.org/view.php?id=16858#c118933 
---------------------------------------------------------------------- 
Your inability to reproduce the problem doesn't detract from the fact that
there is defective code in asterisk. 

The fact that you get '' from the echo test indicates that something (your
system's tty driver perhaps) is masking the bug.

You already have the final answer (the bug fix), you already know your own
different echo test response, so why can't you draw the only logical
conclusion? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-03 20:13 jw-asterisk    Note Added: 0118933                          
======================================================================