# Processing doesn't say where the error is

**URL:** <https://discourse.processing.org/t/processing-doesnt-say-where-the-error-is/46411>\
**Category:** Processing\
**Created:** [May 19, 2025, 8:55pm UTC](https://discourse.processing.org/t/processing-doesnt-say-where-the-error-is/46411 "2025-05-19T20:55:33Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![joshg](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/joshg/32/20226_2.png) [@joshg](https://discourse.processing.org/u/joshg)\
**Post date:** [June 25, 2025, 4:40am UTC](https://discourse.processing.org/t/processing-doesnt-say-where-the-error-is/46411/6 "2025-06-25T04:40:48Z")

</div>

FYI this didn’t get forgotten, and it’s being looked in to.

> <https://github.com/processing/processing4/issues/1153>
>
> \### Most appropriate sub-area of Processing 4?
> 
> PDE
> 
> \### Processing version
> 
> 4.4….4
> 
> \### Operating system
> 
> Ubuntu 24.04, Windows 10
> 
> \### Bug description
> 
> The location of an exception (e.g. NullPointerException) is not highlighted, nor is a stack trace printed. The only information printed is a red NullPointerException message at the bottom. There is no obvious way how to find out where this was thrown.
> 
> This seems to be a regression to earlier 3.x versions, where the line of the thrower would be at least highlighted. 
> 
> 
> 
> \### Steps to reproduce this
> 
> "1. open the below snippet in PDE
> 
> 2. run the snippet
> 
> 3. observe that the error message (NullPointerException) is not linked to any position in the code, nor is any position in the code highlighted, nor is a stack-trace or similar printed anywhere"
> 
> 
> \### snippet
> 
> \`\`\`
> PVector \[\] vs = new PVector\[10\];
> for (int i=0;i\<vs.length;++i)
> vs\[i\].set(0,0); // \<-- this position should be contained in the error message
> 
> \`\`\`
> 
> 
> \### Additional context
> 
> real showstopper when trying to debug any bigger program in PDE!
> 
> \### Would you like to work on the issue?
> 
> No, I’m just reporting the issue

---

_[View the full topic](https://discourse.processing.org/t/processing-doesnt-say-where-the-error-is/46411)._