Hello,
I’m using CVB V 14.1 on Windows 64 bit and Visual Studio 2022. CVB floods the IDEs output window, making me a hard time debugging and stepping through my application while trying to follow my own OutputDebugStrings:
Exception thrown at 0x00007FFEA5DA933A in ImgAcq1.exe: Microsoft C++ exception: GenTLCommon::ExceptionTyped<-1011> at memory location 0x000000F8A8AFF018.
Exception thrown at 0x00007FFEA5DA933A in ImgAcq1.exe: Microsoft C++ exception: GenTLCommon::ExceptionTyped<-1011> at memory location 0x000000F8A8AFF148.
Exception thrown at 0x00007FFEA5DA933A in ImgAcq1.exe: Microsoft C++ exception: GenTLCommon::ExceptionTyped<-1011> at memory location 0x000000F8A8AFF018.
Exception thrown at 0x00007FFEA5DA933A in ImgAcq1.exe: Microsoft C++ exception: GenTLCommon::ExceptionTyped<-1011> at memory location 0x000000F8A8AFF148.
…
Released libraries should not pollute the OutputDebutString space, because users of the library might need to use this api on their own.
So is there a way to disable the many exceptions thrown and handled by CVB internally or any other way to make these messages disappear from my VS2022 output window while leaving my own messages and exception notifications there?
Hi @Jan
I understand that this is not practical having such a huge number of Exception outputs. Especially as they do not refer to an issue.
Beyond that I did not find a way to supress these exception outputs from Visual Studio 2022.
I am in contact with the development team to discuss what options we have. For now I do not have no workaround for you.
Hi @Jan ,
thank you for your question, and yes, we acknowledge the existence of those messages.
The fact, that we throw exceptions (which is normal in c++) is due to internal design and the root cause is not limited to a certain part of our libraries. Therefore, there is no fast and simple solution. This leads us to a very careful consideration on how to cope with that. We have ideas and will look into this.
Hello @s-woe,
Thanks for addressing this issue. If you’re considering how to handle it, I’d like to share my thoughts:
As application software developers, we are CVB customers. And we expect internal CVB issues to not bother us.
The numerous exception messages I’m complaining about occur when CVB can’t communicate with a camera. And that is an expected situation. A single exception entering my code would be fine if necessary. But not a single exception reaches my code, so I can’t handle anything, and therefore the problem is internal to CVB. The problem is that countless exception messages flood my IDE’s output window, making it difficult for me to track the output of my own code and debug the problem.
Imagine your IDE’s output window gets flooded with internal operating system error messages, just because you’re loading and saving files. Thousands of messages like “kernel object access violation” per second. And these messages are irrelevant to you because your file operations are proceeding as expected. So you’re being bothered by things you don’t care about. That’s exactly the situation I find myself in.
I understand, maybe you can believe me, due to the fact that we can see them, too. Maybe we got used to it.
As already mentioned, yes, we know, those messages are there. But, it is not always correct, that they occur when the SDK is not able to contact to the camera. If you consider another perspective: You as a user should not be bothered with exceptions thrown out due to unimportant cases (which the above mentionned exception is). We think the user would be bothered more than usual, if those exceptions would reach the surface. But, we appreciate and acknowledge your concerns and try to improve.
Again: Multiple places in our SDK need to be looked into: The preventable occasions where exceptionGenTLCommon::ExceptionTyped<-1011> are thrown, are prioritized in the solution.