[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #33411] Breakpoints aren't hit with run comman
From: |
Lachlan Andrew |
Subject: |
[Octave-bug-tracker] [bug #33411] Breakpoints aren't hit with run command |
Date: |
Sun, 31 Jan 2016 06:42:10 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 |
Follow-up Comment #8, bug #33411 (project octave):
Rik, it turns out that the reason run isdir didn't return anything is that
run does nothing if its argument is a function not a script.
I've extended the patch to throw an error if the argument to source (used by
run) exists but is not a script. It still silently returns if the file
doesn't exist, so that we don't get an error about ./.octaverc not existing.
The existing code also has a memory leak where the parse tree of the newly
parsed file is not deleted if it is not a script. The patch fixes that too.
(My previous post was also too rushed; I thought that the error messages were
for the run case, not for calling isdir directlly.)
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?33411>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/