Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- gaocegege November 2017
- gohai August 2017
- jeremydouglass August 2017
- kisarur September 2017
Running Processing in Debug Mode
I've started contributing to Processing by trying to fix an issue listed on GitHub. However, I cannot directly trace the exact place where the bug occurs by just looking at the stack trace printed on the Processing console. Can anybody suggest me a method to run processing in debug mode? (Please suggest me if any specific IDE works well for this purpose) Thank you!
Answers
For these kinds of best practice questions, hopefully answers from core github contributors:
https://github.com/processing/processing/graphs/contributors
...who are also on this forum: perhaps @codeanticode @gohai @benfry
@kisarur I am probably an anti-example in that I normally just sprinkle the code with
System.err.println()statements in order to figure things out. Years of writing code with mediocre tooling left their mark on me ;)Thanks a lot for your replies. I was finally able to fix the issue by examining the stack trace and the code a bit more. As @gohai suggests, I also use System.out.println() to track some problems. However, since 'standard out' is not always available in a GUI based app like this, it would be great idea to use 'standard error' to log things. Thanks again for mentioning that trick @gohai :)
I think there is a way to set the mode to DEBUG: https://github.com/processing/processing/blob/master/app/src/processing/app/Base.java#L153
But I failed to get it. Then I removed the condition statement and set the debug to True all the time, it works well for me. /w\