Opened 3 years ago

Last modified 3 years ago

#13032 assigned bug

SerialConnect logs not visible with StyledEdit; error mesaage with Pe

Reported by: vidrep Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Applications/StyledEdit Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

hrev50621 x86_gcc2 SerialConnect->File->Log to file... The logs created by the app are blank when opened in StyledEdit Opening them with Pe brings up an error message See attached screenshot

Attachments (5)

screenshot1.png (208.7 KB ) - added by vidrep 3 years ago.
listattr_serial_log.txt (1.9 KB ) - added by vidrep 3 years ago.
serial_log (130.6 KB ) - added by vidrep 3 years ago.
screenshot1.2.png (206.2 KB ) - added by vidrep 3 years ago.
screenshot2.png (114.9 KB ) - added by vidrep 3 years ago.

Download all attachments as: .zip

Change History (11)

by vidrep, 3 years ago

Attachment: screenshot1.png added

by vidrep, 3 years ago

Attachment: listattr_serial_log.txt added

comment:1 by pulkomandy, 3 years ago

Please attach the problematic file. Is it the one from #13031?

comment:2 by vidrep, 3 years ago

Yes, same file. I'm going to try and replicate the issue on a clean install of hrev50621 x86_gcc2. I'll report the results shortly.

comment:3 by vidrep, 3 years ago

Same thing after doing a fresh install of hrev50621. The file created by SerialConnect comes up blank in StyledEdit. I am able to open the file with both Pe and GoBe Word processing.

Last edited 3 years ago by vidrep (previous) (diff)

comment:4 by vidrep, 3 years ago

I was serial logging thjis morning while testing USB 3.0 cards and seeing the same problem with hrev50677 x86_gcc2. I have attached the file in question as well as a pair of screenshots which show the various error messages when trying to open the file with Tracker, StyledEdit and Pe.

Last edited 3 years ago by vidrep (previous) (diff)

by vidrep, 3 years ago

Attachment: serial_log added

by vidrep, 3 years ago

Attachment: screenshot1.2.png added

by vidrep, 3 years ago

Attachment: screenshot2.png added

comment:5 by pulkomandy, 3 years ago

The serial logs include control characters (mainly for colorizing some things), as a result, they are not really plain text files.

You have also some jamming here, at the transition between the bootloader and kernel logs. This is some unclean initialization in our serial drivers.

This means the message in Pe is expected. StyledEdit could do a "best effort" to open the file still, but it can't accurately convert it to UTF-8, so there will be loss of data.

comment:6 by axeld, 3 years ago

Owner: changed from axeld to nobody
Status: newassigned
Note: See TracTickets for help on using tickets.