ntdll.dll exception when debug with Visual Studio 2003 .net

Question

0.00/5 (No votes)

See more:

Hi,

I have a win32 console app create din VS 2003 .net.

If I compile and run in debug, it crashes after a couple of seconds with an exception coming from ntdll.dll. It does not give any helpful info, everything in the callstack points to ntdll.dll. It didn't always do this, it seemed to be an intermittent problem for a while which I hoped would go away. But it didn't, and now it seems here to stay!

This does not happen when I compile in release and run it.

So I cannot debug my code at the moment.

I was thinking of just starting a new project and copying all my files in and seeing if it happens again, but does anyone know what may be causing this?

Posted 16-Jul-12 1:15am

Jackie Lloyd

Add a Solution

Comments

Richard MacCutchan 16-Jul-12 7:31am

There could be lots of reasons, but it is fairly certain that there is a potential bug in your code. You need to narrow down the problem to the last call out of your code into NTDLL and try to figure out what you may have done wrong. Check all the information provided by the debugger.

Jochen Arndt 16-Jul-12 7:59am

Common errors that can cause such problems are buffer overruns. The exception is thrown when some debug code detects the damaged memory (often when heap memory is released inside destructors). When I have such errors, I will check all pointers and array indices of the classes involved prior to the exception (especially the code that has just been added or changed).

Jackie Lloyd 16-Jul-12 9:19am

Thankyou, I will try all your suggestions. However, what is weird that if I revert to a version of my code from a couple of months ago when I am sure (as i can be) that I didn't have the problem, it now has the problem. And the call stack info is:

=> cccccccc()ntdll.dll! 0x7c903218()ntdll.dll! 0x7c90327a()

ntdll.dll! 0x7c92a98f()ntdll.dll 7c0e46a()(

and that's it - there is nothing else to give me any idea

Richard MacCutchan 16-Jul-12 10:15am

You need to figure out the nearest point in your code to the error, place a breakpoint there, and then use your debugger to step through it until you isolate the bug. There is no way we can figure it out on your behalf since we have even less information than you do.

2 solutions

Solution 2

Thanks to everyone, I did step through and eventually found the problem. Needless to say, you were all right, it was my error (trying to check disk usage on a raid drive that wasn't switched on).
Never again will I try to blame something else! Sorry.

Posted 16-Jul-12 5:43am

Jackie Lloyd

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)

barneyman · Accepted Answer · 2012-07-16T02:02:00

Solution 1

I agree with Richard - I've not seen an exception in ntdll that wasn't actually my fault for years and years now ...

It's normally a broken string or a corrupt pointer - the 'works in release' is a very good indicator it's memory related

What you can try to do is enable OS symbols - downloadable from the MS Symbol server - it makes the stack dump considerably more intelligible - somewhere in options/debug

You may have to update some dll's to make it work[^]

Posted 16-Jul-12 2:02am

barneyman

Comments

Jackie Lloyd 16-Jul-12 9:20am

Thankyou, I will try all your suggestions. However, what is weird that if I revert to a version of my code from a couple of months ago when I am sure (as i can be) that I didn't have the problem, it now has the problem. And the call stack info is:
=> cccccccc()
ntdll.dll! 0x7c903218()
ntdll.dll! 0x7c90327a()
ntdll.dll! 0x7c92a98f()
ntdll.dll 7c0e46a()(

and that's it - there is nothing else to give me any idea

enhzflep 16-Jul-12 11:36am

That's a further indication of it being a memory problem.
You see, the thing is - a program with an error won't necessarily crash - it _may_ do, but it's not a guarantee.

Since your old code that was working is now crashing - but has not been modified, I can confidently say that your old code had the same error.