Project

General

Profile

Actions
Copy link

Bug #6132

closed

Strange behavior of trace command

Added by Mikhail Chupilko almost 9 years ago. Updated almost 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Andrei Tatarnikov
Category:
-
Target version:
-
Start date:
07/02/2015
Due date:
% Done:

0%

Estimated time:
Detected in build:
svn
Platform:
Published in build:

Description

Output trace of this template will include "finishing the loop" and "after the loop" strings.

  def run
    b_imm :end_label # unconditional jump
    trace "inside the loop" 
    nop
    trace "finishing the loop" 
    label :end_label
    trace "after the loop" 
  end

If nop is absent, "inside the loop" will be printed also.
At the same time, none of the strings but only "after the loop" is expected.

Actions
Copy link
 #1

Updated by Andrei Tatarnikov almost 9 years ago

  • Status changed from New to Rejected

This is the expected behavior. Labels, textual outputs, directive etc. are associated with the instruction that comes after them. In fact, they are registered as attributes of this instruction call. Their order is not important. So, it nop is absent, line 

trace "inside the loop"
is associated with the same address as lines 
trace "finishing the loop"
and 
trace "after the loop"
. Consequently, MicroTESK prints all of them.

Actions
Copy link

Also available in: Atom PDF