You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug Description
When using ql.run(count=1) to step through the instructions in the provided assembly code, the expected output "B: Hello folks\n" is not emitted to the console. However, running ql.run() without parameters produces the correct output. The issue appears to be related to the behavior of the ql.run(count=1) function, which may not handle the instruction execution or syscall properly in a stepped execution mode.
Expected behavior
On svc #0, "B: Hello folks\n" is expected to be emitted to the console. This only occurs when ql.run() is ran with no parameters. However, when I step through the instructions using ql.run(count=1), the expected output never appears.
Additional context
I've attempted to capture the output by piping it to a variable but even that is futile. Is there a way to solve this problem?
The text was updated successfully, but these errors were encountered:
ql.runis more suitable for a complete run, as it initializes OS and other components. I believe you should be using ql.emu_start for that. Just use the same begin and end values in the loop, and make sure to set count to 1.
Bug Description
When using ql.run(count=1) to step through the instructions in the provided assembly code, the expected output "B: Hello folks\n" is not emitted to the console. However, running ql.run() without parameters produces the correct output. The issue appears to be related to the behavior of the ql.run(count=1) function, which may not handle the instruction execution or syscall properly in a stepped execution mode.
Sample Code
Expected behavior
On svc #0, "B: Hello folks\n" is expected to be emitted to the console. This only occurs when ql.run() is ran with no parameters. However, when I step through the instructions using ql.run(count=1), the expected output never appears.
Additional context
I've attempted to capture the output by piping it to a variable but even that is futile. Is there a way to solve this problem?
The text was updated successfully, but these errors were encountered: