|
Hello Pete, the first two wishes are possible. Maybe it'll be the easiest, when there will be an extra window, showing the actual code line(s) and the disassembled bytecode, like the outputs of dis.dis / dis.distb. But stepping through single bytecodes isn't possible because the debug events (call, line, exception, ...) are only fired on new lines (see ceval.c -> maybe_call_line_trace). It would require to change the Python VM itself :-( Tobias Hans-Peter Jansen schrieb am 18.04.2017
um 15:52:
On Montag, 17. April 2017 18:42:20 Detlev Offenbach wrote:Hello Pete,the changed indication will be part of the next release. If you need this urgently, please get the default branch of the eric sources.Great, thank you.Detlev PS: Please give a spec for the bytecode disassembler display.Started from a toggle option (e.g. Show Bytecode), python source code lines are amended with the disassembly below (unnumbered). In debug mode, when catching an exception and bytecode display is enabled, the offending opcode should be emphasized in the bytecode disassembly (dis.distb()). See Python build-in dis module and e.g. https://pymotw.com/3/dis/. In a future version, single stepping through the bytecode would be awesome (but I'm not sure, if interfaces for such functionality are available already). Cheers, Pete _______________________________________________ Eric mailing list [email protected] https://www.riverbankcomputing.com/mailman/listinfo/eric |
_______________________________________________ Eric mailing list [email protected] https://www.riverbankcomputing.com/mailman/listinfo/eric
