|
From: | Daniel J Sebald |
Subject: | Re: Connecting Octave to the GUI |
Date: | Wed, 03 Apr 2013 23:02:07 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16 |
On 04/03/2013 10:35 PM, Daniel J Sebald wrote:
I've compiled and I'm coming up to speed on this. I can crash by setting a breakpoint in a file in the current directory. When the debugger stops at that point, I then do a "cd ../<someotherdirectory>" then try to continue. That file has gone out of scope of course.
I've noticed that any breakpoints that are set in a file that goes out of scope because of a "cd" are lost. That info will have to be sent over to the GUI somehow, either as clear all breakpoints for a particular file or individually clear breakpoints. I see that right now the GUI retains the red dots even though Octave currently won't break there again even if the function in the file is run after returning to scope.
However, I wonder why the breakpoints can't be retained and reactivated if the function comes back into scope. Is it that if one changes directory there could be another function of the same name which will confuse the core? The thing is, it would be pretty easy for a GUI user to change directory without being cognizant and breakpoints will be lost. It would be nice if the red dots faded to a translucent color when the file goes out of scope, then come back to solid red if the file comes back into scope.
Dan
[Prev in Thread] | Current Thread | [Next in Thread] |