How do I read and fix a compiler assertion warning ?

Question

0.00/5 (No votes)

See more:

, +

Hello Helpers !

I'm facing a 'warning' when I compile, but I don't understand the messages in the debug box, see below :

com\oleaut32\stdtypes\pictobj.cpp(3103)\ole32.dll!00007FFB26BE4EB6: (caller: 00007FFB26BE59D2) LogHr(1) tid(29f8) 8007029C Un échec d’assertion s’est produit.
com\oleaut32\stdtypes\pictobj.cpp(3103)\ole32.dll!00007FFB26BE4EB6: (caller: 00007FFB26BE59D2) LogHr(2) tid(29f8) 8007029C Un échec d’assertion s’est produit.

It's about an 'assertion fail' but I'm stuck at understanding it for now.
like all parameters in the 2 lines of debug are unknow for me.

if someone have the knowledge to explain me those 2 lines, it will be perfect.

Thank you for the coming help !

What I have tried:

I check and read again my code.
I made few tracing vars, and try, try , try solutions to avoid the message.
I look on search engine a kind of help, but this faulty message seems to be rare through the search engines.

Posted 15-Nov-22 20:23pm

Member 15627495

Updated 15-Nov-22 21:37pm

Add a Solution

Comments

Richard MacCutchan 16-Nov-22 3:44am

Start by checking which OLE calls you are making from your code. You should then be able to use the stack trace in the debugger to find which was the call that led to the assertion.

Dave Kreskowiak 16-Nov-22 8:19am

That's not a compiler error. That is a message that will only show up while your code is running.

You're making a call, either directly or indirectly through a component, to OLE32 and that call was not setup correctly. You're going to have to go through your code up to the point of the failure to figure out why.

Nobody can tell you what you, or the component you may be using, did wrong just from that error message, and that's all you gave anyone to work with.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2022-11-15T21:37:00

Assertions are elements you added to your code to stop execution when an error is detected: Assert method (Visual Basic for Applications) | Microsoft Learn[^]
If you are running under the debugger - and you should be, for testing - then the debugger automatically breaks at the Assert call so you can look at your code and work out why.

We can't fix that: it's something you added to your code and we have no access to that!