Elapsed time logging inserts extra zero

• 报告人: (匿名)
• 属主: (无)
• 类型: Bugs
• 状态: 关闭
• 组件: Tera Term
• 里程碑: Tera Term 4.106 (关闭)
• 优先: 5 - Medium
• 严重性: 5 - Medium
• 处理结果: Fixed
• 文件: 无

Details 回复

When using the elapsed time logging, an extra 0 gets inserted in the log.

Below are two comparisons of a logged bootup from the same Linux embedded device.

The first log was done with local time, the second with the "elapsed time (logging)" option.

As you can see, the SF: 2097152 line took 515ms when using local time logging, but when using elapsed time logging, it reports that it took from 3.0875 to 4.0391s, or 0.9516s. I think it actually took from 3.875 to 4.391s, or 0.516s.

This is a fairly consistent step, bulk loading the Linux kernel from SPI flash, so the speed should be pretty consistent boot to boot.

[2021-05-26 12:03:31.446]  256 Bytes, erase size 64 KiB, total 32 MiB
[2021-05-26 12:03:31.453] SF: 24320 bytes @ 0x70000 Read: OK
[2021-05-26 12:03:31.968] SF: 2097152 bytes @ 0x180000 Read: OK
[2021-05-26 12:03:31.976] Kernel image @ 0x83000000 [ 0x000000 - 0x1ade40 ]

[0 00:00:03.0875]  256 Bytes, erase size 64 KiB, total 32 MiB
[0 00:00:03.0875] SF: 24320 bytes @ 0x70000 Read: OK
[0 00:00:04.0391] SF: 2097152 bytes @ 0x180000 Read: OK
[0 00:00:04.0406] Kernel image @ 0x83000000 [ 0x000000 - 0x1ade40 ]

任务单历史 (2/2 Histories)

2021-05-27 02:16 Updated by: None

• New Ticket "Elapsed time logging inserts extra zero" created

2021-05-27 18:02 Updated by: nmaya

• 状态 Update from 开启 to 关闭
• 处理结果 Update from 无 to Fixed
• 里程碑 Update from (无) to Tera Term 4.106 (关闭)
• 组件 Update from (无) to Tera Term

评论 回复

Hi,

This issue was solved at r8794, and this change will be included in the next release.

Thank you for your reporting.