[Octave-bug-tracker] [bug #48082] Cannot set breakpoint on files that have invalid identifiers as names

[Emma Ainge]

Follow-up Comment #2, bug #48082 (project octave):

Update: 

I thought I had narrowed the bug down to being a problem with naming
conventions. However, I now am having trouble putting breakpoints in normally
named files as well. I am still seeing the error - "error: add_breakpoint:
unable to find the requested function".

I renamed all the files to be names like getdata.m or DataProcessing.m . I'm
not able to put breakpoints in these. I also started fresh with a new script,
pasted in my code, and tried to then add a breakpoint. 

If I start fresh with a new file, named foo.m with a few simple lines of code,
I'm able to place breakpoints without issue. Stumped by this, I attempted to
find where the trouble lies. I started with a fresh file, and bit by bit added
in sections of code. I was able to add breakpoints up until the point when I
added in the following:



%%Thermocouples

for n=1:length(TC(:,1)
    location = find(strcmpi(TC{n,1},TestDataHeaders(1,:)),1);
    eval([TC{n,1} '= TestData(1:end,location);']);
end

%Time



This was the code I originally was trying to use breakpoints to debug. Octave
kept giving me the syntax error for the line that starts with "location =
...". After manually debugging this section of code (without breakpoints), I
found my error is that I need an extra ) on the first line, so that it reads
"
for n=1:length(TC(:,1))". This fixed my code and also resolved the breakpoint
issue. This seems like a bug to me as well, as breakpoints would have helped
me resolve this issue quicker. 

Please advise. Is this a bug? Should I create a separate bug report for this
or leave it here?

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48082>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/