raynebc

Can GPU be specified?

I tried the build Miguel posted but the same two assertion failures are displayed repeatedly several times before the IDE is able to fully launch. In case it matters, in this build, the GetRawData() assertion references line number 1422 instead of the line number I posted back on the forum a long time ago. I am finding that this doesn't happen for every RDP client I use. If I connect to my development computer (running C::B) from a desktop running Windows 10 Enterprise LTSC running build 17763.1158,...

If you can provide a nightly build with debugging symbols I can try to get you a stack trace. I'm not sure the problem described in that link is the same, as the issue I've described isn't random and is reliably reproducible on my end.

Remote desktop causes assertion failures on launch and crashes existing IDE session

Great tools are worth the wait.

Staring in Cppcheck 1.89 I'm seeing a false positive that I can reproduce with this minimal example: void function(int value, char *string) { char *ptr1 = NULL, *ptr2 = NULL; unsigned long count = 0; if(!string) return; ptr1 = string; ptr2 = strrchr(string, 'a'); //The last instance if(ptr2 == NULL) return; //No such instances while(ptr1 < ptr2) { //For each character up to the last instance of 'a' count++; ptr1++; } } I know Cppcheck can't assume the programmer is using pointers properly in such...

In Cppcheck 1.89, I'm seeing a new warning that the previous version didn't give. I was able to trigger this false positive with the following minimal code example: void function(int value) { static int array[16] = {0}; if(value > 15) value = 15; //Bounds check if(array[value]) puts("This element is already nonzero"); array[value] = 1; } The warning would only be valid if it wasn't a static array.

Have you tested this bug in the recently released version 1.84?