|
From: | Richard Crozier |
Subject: | Re: 4.0 release goals |
Date: | Sat, 03 Nov 2012 20:31:13 +0000 |
User-agent: | Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 |
On 03/11/2012 19:55, Max Brister wrote:
On Sat, Nov 3, 2012 at 7:01 AM, Richard <address@hidden> wrote: I compiled without JIT, so I don't know if its related. Adding break points through the editor works, the debugger stops at the break point. However, once I am stopped at a break point and try to use the editor buttons to step through etc. they do not work as expected. I would need to sit and try things out to figure out exactly what happens, but in general on clicking the dbstep button after stopping at a break point, all the debug buttons are deactivated, and the command is ignored in the Octave. There is then though further strange behaviour reported in the Octave terminal, with strange locations being reported by the debug output. I have other problems with debugging though, as reported in bug #37574. Maybe it is something with my setup? This is running Octave using ./run-octave Richard |
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
[Prev in Thread] | Current Thread | [Next in Thread] |