Hello Everybody,
I am trying to debug the genport(portio) driver that comes with the 2000
DDK. I have done the necessary set up for the WinDbg 4.0.0018.0. Configured
the host & target. Made the changes in the boot.ini and all the necessary
steps.
I am able to see the connection between the host & the target. Everything
looks good. But when I put a break point and then I step in the function
GpdAddDevice(), I cant see all the locals. Moreso, it executes the return
statment but doesnt return. It skips a couple of statments. In short, all
the symptoms of mismatch symbols.
I have compiled the code again & again, checked the symbol path, checked for
optimised compilation & linking, swtiched the machines, used a diff pair of
machines. But the result is the same all the time.
More over while doing a kv, it gives a warning about incorrect frames and
stack unwind.
I have a free version of windows 2000 running on host & target.
I am using the checked build env of the 2000 DDK to build the driver.
Am I missing anything?
Has anyone seen such problem?
The system doesnt crash. The driver gets loaded perfectly. But I am not able
to debug it properly.It prints all the DbgPrints also.(correctly)
Kindly let me know if any suggestions/adivces are there.
Regds
Atul
Send and receive Hotmail on your mobile device: http://mobile.msn.com
Try !sym noisy or something like that and then .reload. This will give
you a verbose print trace of what windbg is loading. !drivers will also
show the date for the driver binary.
=====================
Mark Roddy
Windows XP/2000/NT Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com
xxxxx@hollistech.com
For Windows Device Driver Training: see www.azius.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of atul kabra
Sent: Thursday, March 14, 2002 6:27 AM
To: NT Developers Interest List
Subject: [ntdev] Windbg issue
Hello Everybody,
I am trying to debug the genport(portio) driver that comes
with the 2000
DDK. I have done the necessary set up for the WinDbg
4.0.0018.0. Configured
the host & target. Made the changes in the boot.ini and all
the necessary
steps.
I am able to see the connection between the host & the
target. Everything
looks good. But when I put a break point and then I step in
the function
GpdAddDevice(), I cant see all the locals. Moreso, it
executes the return
statment but doesnt return. It skips a couple of statments.
In short, all
the symptoms of mismatch symbols.
I have compiled the code again & again, checked the symbol
path, checked for
optimised compilation & linking, swtiched the machines, used
a diff pair of
machines. But the result is the same all the time.
More over while doing a kv, it gives a warning about
incorrect frames and
stack unwind.
I have a free version of windows 2000 running on host &
target. I am using the checked build env of the 2000 DDK to
build the driver. Am I missing anything? Has anyone seen such
problem? The system doesnt crash. The driver gets loaded
perfectly. But I am not able
to debug it properly.It prints all the DbgPrints also.(correctly)
Kindly let me know if any suggestions/adivces are there.
Regds
Atul
Send and receive Hotmail on your mobile device: http://mobile.msn.com
You are currently subscribed to ntdev as:
xxxxx@hollistech.com To unsubscribe send a blank email to
%%email.unsub%%
> GpdAddDevice(), I cant see all the locals. Moreso, it
executes the return
statment but doesnt return. It skips a couple of statments.
In short, all
the symptoms of mismatch symbols.
Check your SETENV.BAT in the bin folder of the Win2k DDK. The version
of Win2k DDK that comes with MSDN has a bug in it, so that when you
build a driver’s checked version, optimization is not disabled, leading
to symptoms like those you described.
The checked section for i386 should look like:
:checked
rem set up an NT checked build environment
set BUILD_ALT_DIR=chk
set NTDBGFILES=1
set NTDEBUG=ntsd
set NTDEBUGTYPE=windbg
set MSC_OPTIMIZATION=/Od /Oi
:done
If the last set statement is missing, insert it by hand and everything
should work fine. If you need more info, search the list archive for
“locals” AND “WinDbg”.
HTH
Carlo