bugGNU Octave - Bugs: bug #57163, [GUI] Debugger gets confused by...

 
 

bug #57163: [GUI] Debugger gets confused by different pathseps

Submitter:  Philip Nienhuis <philipnienhuis>
Submitted:  Mon 04 Nov 2019 12:03:03 PM UTC
   
 
Category:  Octave Package Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Incorrect Result
Status:  Invalid / Not an Octave Bug Assigned to:  None
Originator Name:  Philip Nienhuis Open/Closed:  * Closed
Release:  * dev Operating System:  * Microsoft Windows
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Tue 05 Nov 2019 09:02:17 AM UTC, comment #10: 

@Markus: yes that exact scenario crossed my mind as well. I tried to reproduce it, & similar scenarios, but that didn't work. Nor interchanging the two installations in that scenario.

@Torsten: I'm confused too :-)

But I'm giving up, I'll close with "Invalid".

Philip Nienhuis <philipnienhuis>
Group Member
Tue 05 Nov 2019 06:08:19 AM UTC, comment #9: 

dbstop is from the CLI, this issue here is in the GUI.

I am confused. The GUI is just using dbstop for setting a breakpoint.

Torsten Lilge <ttl>
Group Member
Mon 04 Nov 2019 11:00:11 PM UTC, comment #8: 

I am guessing the file from the other installation was still open in the editor. When you set a stop point with the GUI, you were asked to add the path to the load path and answered with Yes...

Markus Mützel <mmuetzel>
Group administrator
Mon 04 Nov 2019 10:55:17 PM UTC, comment #7: 

dbstop is from the CLI, this issue here is in the GUI.
Usually stepping into a private function in the GUI just works, however setting breakpoints only works if the private/ subdir is added to the path somehow.

Anyway I'm unsure where the weirdness that I hit came from.

My mxe-octave build tree was started Sept. 1 (but kept up-to-date), so maybe it's better to start a new one. Hopefully that'll fix it.

Philip Nienhuis <philipnienhuis>
Group Member
Mon 04 Nov 2019 10:18:02 PM UTC, comment #6: 

There is bug #41515 about not being able to dbstop in private functions.

Do you agree that this bug here can be closed?

Markus Mützel <mmuetzel>
Group administrator
Mon 04 Nov 2019 09:55:22 PM UTC, comment #5: 

"private folders shouldn't be in the path"

When debugging core functions one sooner or later automatically steps into a private function.
True, one can copy the entire package directory to elsewhere and in the copy move private functions a level up so that they're no more private. But that's a lot of hassle.

Philip Nienhuis <philipnienhuis>
Group Member
Mon 04 Nov 2019 04:48:07 PM UTC, comment #4: 

I also see the random crashes when using "F9". It feels like it is more frequent when I'm in the debugger.

I believe "private" folders shouldn't be in the path. Maybe that's why Octave used a function from the different installation. I don't know what the precedence order is in this case.

Markus Mützel <mmuetzel>
Group administrator
Mon 04 Nov 2019 04:22:02 PM UTC, comment #3: 

Yep, different paths. So the dep on bug #56267 is moot.

_Can you please elaborate what is wrong?_

Well, some strange mixup here.
The debugger somehow stepped into a private module from another installation (that I had loaded in the editor earlier in the same session to compare); no idea how that program flow went. The path popup is real.

Bug #57146 is also (still) playing up here and at times Octave crashes unpredictably when pressing F9. No certainty those are related.
I'm trying to assess a reproducible scenario.

Philip Nienhuis <philipnienhuis>
Group Member
Mon 04 Nov 2019 12:28:32 PM UTC, comment #2: 

Those are two different paths (note the date) both seem formatted correctly. Can you please elaborate what is wrong?

Markus Mützel <mmuetzel>
Group administrator
Mon 04 Nov 2019 12:08:30 PM UTC, comment #1: 

When clicking "Add to load path" I get this:

>> path

Octave's search path contains the following directories:

.
D:\Octave\Octave-6.0.0_20191102L\mingw64\share\octave\6.0.0\m\pkg\private
D:\Octave\Octave-6.0.0_20191031L\mingw64\share\octave\6.0.0\m\pkg\private


so the fix for bug #56267 (about double entries) might be insufficient.
Adding that report as dependency and cc-ing Markus.

Philip Nienhuis <philipnienhuis>
Group Member
Mon 04 Nov 2019 12:03:03 PM UTC, original submission:  

This bug is undoubtedly related to the fix for bug #56267.

When stepping into a function that is in the path, the debugger does not recognize it is in the path because it mixes up forward and backward slashes.
Compare this:

>> path

Octave's search path contains the following directories:

.
D:\Octave\Octave-6.0.0_20191031L\mingw64\share\octave\6.0.0\m\pkg\private


with attached pic.

Philip Nienhuis <philipnienhuis>
Group Member

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files

 

Digest:
   bug dependencies.

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by ttl (Posted a comment)
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by philipnienhuis
  • -email is unavailable- added by philipnienhuis (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-11-05 philipnienhuis Open/ClosedOpen Closed
    2019-11-05 philipnienhuis StatusNone Invalid / Not an Octave Bug
    2019-11-04 philipnienhuis Dependencies- Depends on bugs #56267
    2019-11-04 philipnienhuis Carbon-Copy- Added mmuetzel
    2019-11-04 philipnienhuis Attached File- Added Debug_pathsep.PNG, #47802

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code