[Simulavr-devel] [bugs #8457] simulavr-disp displays garbage characters after "Reserverd"

[Theodore A. Roth]

This mail is an automated notification from the bugs tracker
 of the project: Simulavr: an AVR simulator.

/**************************************************************************/
[bugs #8457] Latest Modifications:

Changes by: 
                Theodore A. Roth <address@hidden>
'Date: 
                Wed 04/07/04 at 18:13 (US/Pacific)

------------------ Additional Follow-up Comments ----------------------------
The problem is you are mixing terminal output with stdout/stderr. The -X option 
was really added to allow a display program to be run without an xterm under 
the assumption that it wouldn't need to output to a terminal (e.g. it used a 
GUI).

One possible solution would be to add a --logfile option to send all of 
stdout/stderr to a file instead of to the screen.






/**************************************************************************/
[bugs #8457] Full Item Snapshot:

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=8457>
Project: Simulavr: an AVR simulator
Submitted by: Eric Weddington
On: Mon 04/05/04 at 17:21

Category:  None
Severity:  5 - Average
Item Group:  None
Resolution:  None
Assigned to:  None
Originator Email:  address@hidden
Status:  Open


Summary:  simulavr-disp displays garbage characters after "Reserverd"

Original Submission:  Version: 0.1.2.1
Using: simulavr -X -P simulavr-disp.exe -d atmega128 -g, from a Cygwin build of 
simulavr.

The "IO Registers" portion of simulavr-disp will show some trailing garbage 
characters after the word "Reserved". This is seen in both Cygwin's bash shell, 
and the Windows command-line shell.


Follow-up Comments
------------------


-------------------------------------------------------
Date: Wed 04/07/04 at 18:13         By: troth
The problem is you are mixing terminal output with stdout/stderr. The -X option 
was really added to allow a display program to be run without an xterm under 
the assumption that it wouldn't need to output to a terminal (e.g. it used a 
GUI).

One possible solution would be to add a --logfile option to send all of 
stdout/stderr to a file instead of to the screen.












For detailed info, follow this link:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=8457>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/