Why printstacktrace should be removed

Or can I ignore this? It is just a recommendation. In eclipse it is fine - I believe it is just the IDE telling you that there are more conventional methods of doing it, like some of the other answers.

I find that it is useful for debugging, and that you should tell users when a fatal error is going to occur, to use a debug mode like a console switch -d to collect these logs. PHP is evaluated on the server before the page is sent to your browser.

By the time the browser sees it and executes the javascript, all the PHP is gone. Use your browser's "view source" on the browser window with this code in it. You'll see it looks like this:. You either need to implement what you want to do in javascript to run on the browser, or you need to send a new request to the server and get a new page back either directly or indirectly with your response.

However, it a nice idea to just allow certain types of user agents. I would also suggest that it's better to use a logger rather than System. Campbell Ritchie. Probably because printStackTrace is so very basic. It displays information which is useful for development, but the user will have an incomprehensible printout, which will simply be forgotten. Alvin Watkins. I use printStackTrace with regularity. I don't use a logger like Log4j often - it's great to use if you need it though because the only time anyone should see errors relevant to stack traces are in development and they are very useful to me.

Of course, I also return some message to the user in production so that the UI can inform the user of what's going on. In a production environment, however, no one should ever see a stack trace and if a stack trace is printing, it's probably indicating that I have an issue I need to fix in the code.

Alvin Watkins wrote: the only time anyone should see errors relevant to stack traces are in development Stack traces are also a useful diagnostic tool in production. The end user shouldn't see them of course, but they can be invaluable to the developer for tracking down problems that are hard to reproduce in a dev environment.

Jeff Verdegan wrote: You might see if NB offers something similar. The text was updated successfully, but these errors were encountered:. Skip to content. Star New issue. Jump to bottom. Milestone 6. Linked pull requests.

Copy link. A stack trace is generated whenever application crashes because of an error or an exception.