Call stack never shows our own code
Debug -> Threads -> [pick a thread, any thread...] showing up only kernal
call stack.
I observed this when a thread is waiting on a system call such as Sleep,
WaitObject or EnterCriticalsection. The situation improved after I
prevented the debug symbols for NTDLL.DLL being loaded and load all other
symbols. I still have problem viewing my call stack when a thread is
waiting in WaitForSingleObject call (This call results in direct call to
NTDLL.DLL). Any suggestion? (I am a old time with NT4.0-SP5 and VC5.0-sp3).
Thanks
Anand Bosco
Quote:
>Greets,
> Shhh! Don't give away all the secrets now. It's more fun when they
>discover them on their own! :)
>Regards,
>Joe
>> Debug -> Threads -> [pick a thread, any thread...]
>> > Greets,
>> > Does one have any way to work up the call stack with their de{*filter*}
>or
>> > perhaps the capability to switch threads? It might be a bit
>enlightening.
>> > :)
>> > Regards,
>> > Joe
>> > > Hi all,
>> > > We're having a problem with the break command when debugging a debug
>> build
>> > > under win2k pro. We always break out into the kernel call stack,
>rather
>> > > than our own code. Manually setting breakpoints works fine. This has
>> only
>> > > started happening since we moved to win2k from 98 - anyone with any
>> ideas?
>> > > The system specs are: PIII 600, 512Mb RAM, Win2k Pro, MSVC6 SP4.
>> > > Thanks in advance.
>> > > Chris