How to detect Release crash that is not produced on Debug

[^NyAw^]

Hi,

Ok, maybe I'm a little bit too hard.

Yes, is what I felt.

Programming is a lot more than just sitting behind your pc and writing a little program as a hobby.
You need to educate yourself to an engineering level to understand what goes on inside a computer. I do not pretend to know all of this as computer sciences are not my main speciality.

I know a little bit programming, I've been 5 years programming on this project that I started myself. It's a machine vision application that uses multiple threads, multiple I/Os, ... and it works well.

But what I do know, and this is from experience, is that you can certainly debug applications without debugging symbols in a debugger. But you'll need to know how the computer, the operating system, the compiler and the debugger work.

This is what I didn't know. I thought that I need to tell the compiler to gereate the debugging information to let the debugger debug it.

As suggested above, nothing stops you from including a logger in your program to log debugging messages just like if you use qDebug().
But if that fails, you'll need to use a debugger.

It's just a bit complicated. As I told, it uses multiple threads, but could be helpful on some situations.

One of your next questions could have been: "Where do I find more information about debugging my program?"
I would have responded with: "A good place to start is the documentation of the debugger you're going to use."

Ok, so if anyone knows how to debug my aplication compiled in release mode on Visual Studio debugger it will be great.

Another question could have been: "Can I compile my program in release mode and still have all my symbols available somewhere?"
I would have responded with: "Of course you can, see the manual of your compiler and debugger. You can even split everything up!"

This is what I need.

Another question could have been: "What exactly is the difference between a debug and release?"
Even another question could have been: "Why do I get this error in release mode? Does it have something to do with my compiler optimizing some critical code that I didn't guard so well in my application?"
etc...

I know about the code optimizations. Read my post, I told that the application had been working well for a lot of time on the target machine.

Did you ever see a crash log in Windows? Can you make sense of it?

No, I didn't check it never. I don't know where to start getting relevant information on it, ...

The same can be said with programming. Most people can write program code. But when you get into a situation where you are now, it takes experience and knowledge to understand what goes wrong and to solve it.

[/QUOTE]
Yes, I know. I'm sure that I'm not a begginer.

Thanks,

The other question is. Anyone have experienced problems when calling "flush()" from a thread that was created on the main thread?

Thanks,