[asterisk-bugs] [Asterisk 0016858]: asterisk command history loads as unusable garbage
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Mar 3 17:53:01 CST 2010
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 17:53 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.
======================================================================
----------------------------------------------------------------------
(0118919) qwell (administrator) - 2010-03-03 17:53
https://issues.asterisk.org/view.php?id=16858#c118919
----------------------------------------------------------------------
>> jtodd said: "History works fine on MacOS 1.6.2". He did not mention the
minor
>> revision. He did not mention whether retrieval of saved history works
... just
>> that history works. He didn't mention what localized patches might have
been
>> applied.
>>
"History works" means that all of it works for him. When somebody gives
the name of a branch they've tested, it means they were testing on the
latest revision of that branch.
>> imadsen didn't indicate what version was working for him.
>>
He absolutely did. He said "Asterisk trunk".
>> The answer to the questions have already been supplied. The bug report
states
>> what version it relates to. The platform is Linux Fedora Core 12 but it
has
>> been compiled from new source (not the fc12 supplied version), so the
platform
>> is largely irrelevant.
>>
You did not supply the platform until just now. Yes, it is very relevant.
You still have yet to actually describe the issue you're seeing.
>> For goodness sake ... if this is the attitude taken when there is a
blatant
>> bug (I suppose nobody has bothered to even read the source - it is so
obvious)
>> then no wonder asterisk is so bug-ridden.
>>
Neither jtodd nor lmadsen gave you any attitude. However, if you're going
to flame our bug marshals and developers while not giving us any useful
information - yes, I am going to call you on it.
>> FYI I have already patched my asterisk to fix the bug - basically by
replacing
>> the body of funtion ast_el_read_history() with:
>>
SNIP
>> And, of course, it fixed the problem!
>>
>> Is that any help?
>>
Not in the least. Once again - you have not even described the issue you
are seeing.
Issue History
Date Modified Username Field Change
======================================================================
2010-03-03 17:53 qwell Note Added: 0118919
======================================================================
More information about the asterisk-bugs
mailing list