Switch to full style
Discussions about Coollector.
Post a reply

Coollector LOG

Thu Nov 02, 2017 4:18 pm

I have seen that you face a lot of problem when users speaks about the bugs and issues and you had difficulties to go in depth of the situation.

So as per the developer point of view, what I found the best is that you introduce a log file which will record the log entry each time the user do some activity. And in this way neither the user not you have to bang your head to look for how to replicate the bug or how to recognize the issue.

My suggestion might not be the best way but this is what I come up with. :) :) :)

Re: Coollector LOG

Thu Nov 02, 2017 6:07 pm

Abubakar Siddique wrote:I have seen that you face a lot of problem when users speaks about the bugs and issues and you had difficulties to go in depth of the situation.

When the program crashes, it creates a crash dump, but I can't "go in depth" with this dump because it doesn't contain enough information because it was produced by the release version of Coollector,.

On the contrary, if It's a debug version and it crashes, contrary to the release version the dump will this time allow me to make a deep analysis and understand the problem.

So when a user faces a hard to explain problem, I build a debug version for him to try to produce a useful crash dump.

Re: Coollector LOG

Thu Nov 02, 2017 7:43 pm

oh so you already have an alternative way to handle the situation.

But I think adding a log entry system would be more reliable. :roll:

Re: Coollector LOG

Thu Nov 02, 2017 9:39 pm

Abubakar Siddique wrote:But I think adding a log entry system would be more reliable. :roll:

The program would probably crash before it could log anything interesting.

The crash dumps are amazing. I can see exactly where the program crashed, with the value of each variable.
Post a reply