nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Breakpoints in Rhino Debugger

medini_1035403171

Hello everyone!

It seems that Rhino
Debugger does not handle one of my files appropriately when debugging. The file is included/imported in the main
scripting file.

First is, the breakpoints cannot be
set correctly. I have to set them one line above the line I want to use (see
screenshot with all possible breakpoints for the first few lines).

Second is, when
I edit the file and start debugging, I still start with the previous version
and have to restart debugging. Even then it does not work reliably and the breakpoints are still wrong.

This only occurs with this one certain file. I tried to recreate it, to rename it. It did not help. Has anyone had similar experiences? Any advice from your side?

Thanks,

Johannes

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Hello Johannes,

I checked the issue quickly and can confirm that there is indeed a problem with the line numbering. Its correct for the main script but not for scripts loaded via "load". We can fix with next release end of April.

The second problem I could not reproduce. Once a file is changed (either main or imported). The debugger reloads it and discards all breakpoints. That's how it works on my end.

Anything special to the file or to your changes?

I was adding / removing empty lines.

Jan

All comments

medini_1024169437

Hello Johannes,

The second problem I could not reproduce. Once a file is changed (either main or imported). The debugger reloads it and discards all breakpoints. That's how it works on my end.

Anything special to the file or to your changes?

I was adding / removing empty lines.

Jan

medini_1035403171

Hello Jan,

Good to hear that you could reproduce the first behavior.

Talking about the second one, is it possible that the file is only updated after executing the load command in the main file or after entering it with the "instruction pointer" during debugging? If you start the script in debug mode, it will stop in the first line of the main file. Then please minimize the main file in the debugger window and have a look at the second file. Does it show the new or old version? Maybe this is the point.

Cheers,

Johannes

medini_1024169437

You are right, Johannes. I encounter the same behavior. Since "load" simply means, "read and evaluate the script", its at the time the load function is called. So whenever load is called, in my case the new file is shown in the debugger. And with the fix in place for problem 1, the break points are not removed.

Regards

Jan

medini_1035403171

Thanks for your answer, Jan. From my point of view it would be helpful if the files got updated when the debugging is started so that you can set breakpoints at edited lines of files included via "load" before actually starting the script.

Cheers,

Johannes

medini_1024169437

Johannes, the debugger issue was fixed in 2019 R2.

Happy Scripting

Jan