processing / processing/processing4
Debugger not breaking on 4.0b8 on MacOS Monterey – Depends on file name.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 494
- Forks
- 183
- Avg merge
- 4h 39m
- Merged PRs (30d)
- 3
Description
Created by: 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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the debugger behavior on macOS Monterey using the original and copied six-line sketches, then compare the filenames and parent folders, including names with underscores. Start by checking how the debugger associates breakpoints with sketch files; done means identifying the filename-dependent cause and confirming that breakpoints work without renaming files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100