Re: debugging/ NTDLL.DLL/ and more

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

can you explain, please?

1. where/how do i get good symbols for the OS binaries?
i have installed windows symbols from microsoft.com (debugging),
but i don't see them in my disassembly.
2. and what means "posting a stack"? do you mean,
putting a message in the newsgroup with a copy of the call stack?
3. what means "thunk" in: "....and thunk against the native calls......"?

regards,
mk

"Ivan Brugiolo [MSFT]" <Ivan.Brugiolo@xxxxxxxxxxxxxxxxxxxx> schreef in
bericht news:%23VU91CVHGHA.3532@xxxxxxxxxxxxxxxxxxxxxxx
> ntdll.dll is a core OS module responsible to implement
> runtime functions (String Conversion, Heap management, Generic containers)
> and thunk agaisnt the native calls implemented in the kernel.
>
> In 99.99% of the cases, a problem in ntdll.dll is a consequence of
> a programming error in the application, that causes the internal state
> of the runtime in ntdll.dll to get corrupted.
>
> First thing that would come to mind is a heap corruption.
> If you could get good symbols for the OS binaries, and post a stack,
> maybe few people could be able to help.
>
> --
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of any included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
>
>
> "marco 2" <rebel-6-out@xxxxxxxxx> wrote in message
> news:43d0111d$0$12831$ba620dc5@xxxxxxxxxxxxxxxxxxxxxx
>> hi everybody!
>>
>> please help!
>>
>> in my vstudio 2005 solution i recieve an error when i start
>> without debugging.
>> it's an unhandled excpetion - access voilation - reading from 0x0000
>> - inside NTDLL.DLL
>>
>> 1. what is/does ntdll.dll?
>> 2. how should i resolve/debug this error???
>> i have little or no experience in debugging, especially
>> in vc++ and winXP, so please tell me how to debug this
>> and other things! years ago i worked in motorola and pentium assembly,
>> and i knew how to debug it, but not inside vstudio 2005.
>>
>> regards,
>>
>> marc k.
>>
>>
>
>


.

Relevant Pages

  • Re: debugging/ NTDLL.DLL/ and more
    ... > i have installed windows symbols from microsoft.com (debugging), ... > putting a message in the newsgroup with a copy of the call stack? ... >> First thing that would come to mind is a heap corruption. ... >>> and i knew how to debug it, but not inside vstudio 2005. ...
    (microsoft.public.vc.language)
  • Re: CURRENT freezes on Laitude D520
    ... really exists for the purposes of supporting components which are not sufficiently locked to allow the stack to run MPSAFE, rather than as a means of disabling direct dispatch and preemption, which speak to different types of problems. ... INVARIANTS, DDB, KDB, and BREAK_TO_DEBUGGER to debug deadlocks. ... In RELENG_6, PREEMPTION is in GENERIC and hence enabled by default, and it can be disabled by removing it from your kernel configuration. ... However, this is also just a debugging step to see if that quiesces the problem, and not a fix for the actual bug. ...
    (freebsd-current)
  • Re: Iteration in lisp
    ... FUNCTION CALLS, HAZARDOUS TO YOUR STACK SPACE, USE AT YOUR OWN RISK. ... - The concise code typical of Scheme is self-explanatory. ... debugging errant programs was a routine problem that could be ... How do Scheme programmers debug their code?? ...
    (comp.lang.lisp)
  • Re: Differences in unhandled exception handling between Windows 2000 and 2003?
    ... it will be caught very nicely by my favorite debugging procedure du ... the thread that just took the exception. ... I really don't think it's stack. ... so I have a good vehicle for implementing a minimal debugger. ...
    (microsoft.public.win32.programmer.kernel)
  • Windows XP with bluescreen parport.sys
    ... Here is the complete bluescreen I debugged with the Windows Debugging Tools: ... After setting your symbol path, use .reload to refresh symbol locations. ... a driver actually attempted to complete its own packet ... stack for the current request can be found by examining the DeviceObject ...
    (microsoft.public.windowsxp.general)