dadasg.blogg.se

However, when I ran a test script, it produced some unexpected output. Which worked as expected with the poll call returning None.

Spike = Popen(, stdin=PIPE, stdout=PIPE, stderr=STDOUT) I first used the following code to make sure that the process was booting correctly (the script is running in the same folder as a.out and spike is on the system path): from subprocess import Popen, PIPE, STDOUT The problem arises when I attempt to run the program through Python's subprocess Popen object. Where the text after (spike) is user input, and a blank afterwards just means enter was pressed immediately. Typically, a session in Spike's interactive debugger looks as follows: (spike) pc 0Ĭore 0: 0x0000000000001000 (0x00000297) auipc t0, 0x0 I have Spike running on a Debian system in WSL. I have been attempting to write a wrapper program around Spike's interactive debug mode on ( ) in Python 3 to provide additional functionality that is not present in the base program.