[Bug 1000714] New: RedBoot command history numbering mismatch

[Bug 1000714] New: RedBoot command history numbering mismatch

[bugzilla-daemon]

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000714

           Summary: RedBoot command history numbering mismatch
           Product: eCos
           Version: 3.0beta1
          Platform: Other (please specify)
        OS/Version: Other
            Status: NEW
          Severity: normal
          Priority: normal
         Component: RedBoot
        AssignedTo: gary@mlbassoc.com
        ReportedBy: john@dallaway.org.uk
         QAContact: ecos-bugs@ecos.sourceware.org
             Class: ---


The numbering of previous RedBoot commands as presented by the "history"
command falls out of sync with the numbering used by the "!<n>" command recall
mechanism once the history buffer is full (16 commands by default). This can
lead to a command being executed unintentionally.

It appears that the "!<n>" system will always invoke one of the initial 16
commands entered following system reset, but the "history" command will present
the most recent 16 commands.


-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

[Bug 1000714] RedBoot command history numbering mismatch

[bugzilla-daemon]

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000714


Gary Thomas <gary@mlbassoc.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |CURRENTRELEASE




--- Comment #1 from Gary Thomas <gary@mlbassoc.com>  2009-03-09 23:49:16 ---
Fixed by keeping a virtual command number which allows proper tracking
of commands which are in the circular buffers.


-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.