It's the first case, an app that I control, I am the developer of the app. The idea is that if something goes wrong (we will be logging to the stderr in case of ungraceful exits), the user or support team of the application can rerun the app from a terminal and they’ll see the stderr logs on the console or redirected to a file.

It is the first case, an app that I control as a developer. The idea is that if something goes wrong (All these kinds of apps will log to stderr due to ungraceful exit), the user or support team can rerun the app from a terminal and they’ll see the error logs on the console.

It is the first case, an app that I control as a developer. The idea is that if something goes wrong (All these kinds of apps will log to stderr due to ungraceful exit), the user or support team can rerun the app from a terminal and they’ll see the error logs on the console.

It is the first case, an app that I control as a developer. The idea is that if something goes wrong (All these kinds of apps will log to stderr due to ungraceful exit), the user or support team can rerun the app from a terminal and they’ll see the error logs on the console.

Hi, Thankyou for your response. Yes, although the the system log is the more recommended way, I am working on a cross platform application, and thus implementing the stderr in C++ will be more easier to maintain. Also, logging to the stderr is the extreme last resort for my application and I expect it to occur once in a thousand times.