Project

General

Profile

Bug #9333

unexpected hex value in MIPS trace

Added by Sergey Smolov over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
10/17/2018
Due date:
% Done:

100%

Estimated time:
Detected in build:
qemu4v.master
Platform:
Published in build:
0.2.4-beta-181112

Description

At the beginning of trace part, that is related to test program, an unexpected hexadecimal value appears (here is is surrounded by '*' symbols for better readability):

38 clk 0 IT (38) ffffffffbfc0fffc nop
*0xffffffffbfc10008*39 clk 0 IT (39) ffffffffbfc10000 j 
40 clk 0 IT (40) ffffffffbfc10004 nop
41 clk 0 IT (41) ffffffffbfc10008 mfc0 t8,$16
42 clk R $t9 ffffffffffff0000
42 clk 0 IT (42) ffffffffbfc1000c lui t9,0xffff

This value should be excluded from MIPS trace.
To reproduce the bug, run run_test.sh script from q4v.tracing branch of MicroTESK for MIPS64 project.

History

#1

Updated by Sergey Smolov over 1 year ago

  • % Done changed from 0 to 100
  • Assignee changed from Maxim Chudnov to Sergey Smolov
  • Status changed from New to Resolved
#2

Updated by Sergey Smolov over 1 year ago

  • Detected in build changed from master to qemu4v.master
#3

Updated by Sergey Smolov over 1 year ago

  • Published in build set to 0.2.4-beta-181112
  • Status changed from Resolved to Closed

Also available in: Atom PDF