Sun 02 Apr 2017 10:40:21 PM UTC, comment #11:
Hi,
I had the same problem on Octave when testing pmtk3 package, on Ubuntu 16.04
error: remove_breakpoint: unable to find the requested function
I tried to apply the patch but it did not work. Can you please publish the Ubuntu patch?
Multiple thanks!!
|
Sun 19 Jun 2016 11:30:50 AM UTC, comment #10:
Hi there,
I am new to Octave and I was wondering if I can apply the patch mentioned below in order to repair my Octave 4.0.2 on Windows.
Can someone give some hint about how I can find out to proceed?
Thanks,
Daniel
|
Mon 08 Feb 2016 12:27:55 AM UTC, comment #9:
Unfortunately I'm not that familiar with the internals of classdef. About who wrote it, I believe it was mostly Michael Goffioul.
|
Sun 27 Dec 2015 01:46:37 AM UTC, comment #8:
Carnë, the attached patch allows breakpoints to be set with the syntax
dbstop classname>method
Could you please give it a try?
It has a memory leak. The problem is that the classdef framework doesn't seem to keep octave_user_function objects around, but instead creates octave_function objects on the fly. In order to keep them around long enough for the dbstatus and dbclear commnds, I'm just allocating them on the heap :( The patch is clearly not ready to be applied, but I hope it may help someone who knows more about classdef. Do you know who wrote that code?
Thanks
(file #35861)
|
Wed 23 Dec 2015 11:24:59 PM UTC, comment #7:
I now see that I had old class definitions in my path. Without thme, I get the same problem. It turns out that it does find the constructor, but that it is not considered "user code" (it is not of type octave_user_function) and so doesn't set the breakpoint.
Unfortunately, the classdef framework doesn't seem to have clear "tree_statement_list" objects into which the breakpoint can be placed. I'm intrigued by this and will keep looking into it.
|
Mon 21 Dec 2015 03:56:05 AM UTC, comment #6:
Carenë, it's odd that it works for me but not for you. Bug #46468 reports the same problem, so I'm the odd one out. Are you using Windows?
|
Tue 15 Dec 2015 02:12:39 PM UTC, comment #5:
I tried at a88142abca36 like you and continue to see "add_breakpoint: unable to find the requested function"
This is the same I saw on 4.0.0 and 8da80da1ac37 (current tip of default branch).
|
Tue 15 Dec 2015 03:48:26 AM UTC, comment #4:
Carnë,
I just re-checked it on the default branch at changeset a88142abca36 ("Remove spurious tick labels occurring when setting ticks and removing tick labels")
Even though it doesn't appear in dbstatus, it does appear to stop in that function:
Running dbstatus clears the breakpoint, as described in bug #41190.
|
Mon 14 Dec 2015 07:27:37 PM UTC, comment #3:
What octave version are you using that returns:
|
Sat 12 Dec 2015 10:18:22 PM UTC, comment #2:
Oops. I spoke too soon. Although it reported a line number, it didn't show up in dbstatus. I'll keep investigating.
|
Sat 12 Dec 2015 09:53:57 AM UTC, comment #1:
Carnë,
>> dbstop ("@inputParser/inputParser")
ans = 130
I think the bug is in the documentation. Should I post a patch?
|
Sun 15 Nov 2015 07:15:32 PM UTC, original submission:
It seems that it is not possible to set a breakpoint within a classdef class.
This may be related with not being able to define a classdef on the interpreter or why "which" does not associate it with a file.
|