Debugger not breaking on 4.0b8 on MacOS Monterey – Depends on file name.

[alsmithson]

• I opened a sketch written by someone else and tried to use the debugger. It would not break on any line.
• I reduced the code down to 6 simple lines and it still would not break.
• I copy/pasted the code to a new, blank sketch, and breakpoints did work.
• After saving both files that only had 6 lines of code, I looked at the code with Atom and DiffMerge. Neither could find a difference except for the file name.
• I renamed the two files to good.pde and bad.pde and renamed their parent folders to match. Now both sketches break correctly.

I have another sketch by the same author with the same behavior. I could not see anything odd in the file name (though it did use underscores). I copy/pasted the file name into Atom and looked at the Hex code. Nothing was out of place, but I’m not sure my Mac did not do a conversion in the clipboard. The author speaks Spanish and lives in the Canary Islands, so maybe his keyboard is different from mine.

I have a workaround (renaming all files), but I wanted to report this odd behavior.

[benfry]

Very odd; thanks for the details.

[Heerema]

I am also encountering an issue where the debugger will not break. I've used both the Apple Silicon and the Apple Intel version of Processing 4.3, running under macOS Sonoma.

This sketch spans a number of source files ... and annoyingly, if the program encounters an exception, the reported line number is just nonsense - it looks like all of the files are concatenated, and the reported line number is the line in the concatenated file (good luck translating this to a line number in one of the source files).