|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #47605] dbwhere hangs after debug_on_error stops Octave |
Date: | Mon, 04 Apr 2016 17:55:42 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 |
Follow-up Comment #6, bug #47605 (project octave): Here's a clue: >> debug_on_error (true); >> ls asdfasdfasdf stopped in ../scripts/miscellaneous/ls.m at line 99 99: error ("ls: command exited abnormally with status %d\n", status); debug> dbup stopped in ls at line 99 [../scripts/miscellaneous/ls.m] debug> dbwhere stopped in ls at line 99 [../scripts/miscellaneous/ls.m] 99: error ("ls: command exited abnormally with status %d\n", status); So everything works if a dbup is done first. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?47605> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |