User forums > Help

V 20.03 startup fails w/debugging assertion failure if not running as admin

(1/3) > >>

caonen8425:
Running C::B on Windows 7 Pro 64

Just installed v20.03 a few days ago.  About day 2 into using it, startup began failing with a 'debugging check...assertion failure' in GetWeightClosestToNumericValue(). Screen snippet attached (hopefully).  I never quit out of C::B with the debugger running. Admittedly, during the time period this failure began, I was still tweaking the toolchain and search directory settings, so that is certainly suspect. But I fail to understand how ensuring the use of 64-bit tools, libs, et al would throw a debugger check assertion at startup when the debugger is not even running.

If I start C::B with 'run as administrator', the error does NOT occur.

In all other respects, to-date, v20.03 has been solid for me.

I've never before needed to run C::B with admin privileges, and it seems insane to do so unless needed by the specific app under development.

oBFusCATed:
What happens if you click continue?

This is supposedly a known problem in wx which we should have fixed.
@Killerbot have you applied the patch for the font issue to our version of wx?

killerbot:
which specific path are you talking about ?
I will compare with the patches I have carried out, somewhere described in the forum, but also in a log file in my windows partition.

oBFusCATed:
The one related to the fonts or fontinfo. There was some rounding problem. Ollydbg reported it and it was fixed.

stahta01:
Attached patch file. I am using to patch wx3.1.3.


--- Quote ---
Date: Thu, 16 Jan 2020 00:07:06 +0100
Subject: Allow parsing all fractional sizes in wxFont descriptions

--- End quote ---

Tim S.

Navigation

[0] Message Index

[#] Next page