|
From: | Philip Nienhuis |
Subject: | [Octave-bug-tracker] [bug #57902] Confusing debug output from scripts |
Date: | Wed, 26 Feb 2020 14:00:17 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0 |
Follow-up Comment #2, bug #57902 (project octave): Sorry for not mentioning right away: Selecting the code and pressing F9. That is how I hit this on my work desktop (Windows 7 Enterprise). On my home desktop (Windows 7 Professional) the very same crossbuild works differently. Running the script/code (from the command line or selecting the code and then pressing F9) catches the "keyboard" statement. From then on, the first dbstep seems to do nothing; the second dbstep makes Octave crash. I can quite reliably reproduce this. But sometimes it goes through and after using several "dbstep"s execution proceeds. Note: This is with your cset 262cdfc6faf9 (comment #7 in bug #57439) backed out because with it I found Octave much too slow to be useful. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?57902> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |