I am debugging the dus driver for the first time.Now I am able to apply a
breakpoint in a file . But when the flow comes at the breakpoint, it gives
the control in my hand but the source code I see on debugger is
ASEMBLEY.BUt I want the source code to debug.I got to know that there is
special option in the build command.I tried to search it but I didn’t see
any such option. I have gave the build -ceZ option. So can u tell me that
option?I am using windbg 6 now.
Anand.
Hi,
Have you set the source file path in the debugger?
Regards,
Rajiv.
-----Original Message-----
From: Anand [mailto:xxxxx@lambenttek.com]
Sent: Tuesday, August 06, 2002 10:14 AM
To: NT Developers Interest List
Subject: [ntdev] assembly code at breakpoing.
I am debugging the dus driver for the first time.Now I am able
to apply a
breakpoint in a file . But when the flow comes at the
breakpoint, it gives
the control in my hand but the source code I see on debugger is
ASEMBLEY.BUt I want the source code to debug.I got to know that there is
special option in the build command.I tried to search it but I
didn’t see
any such option. I have gave the build -ceZ option. So can u
tell me that
option?I am using windbg 6 now.
Anand.
You are currently subscribed to ntdev as: xxxxx@wipro.com
To unsubscribe send a blank email to %%email.unsub%%
Hello all,
I got ur point.I checked that source path field and found it is already
filled by the debugger.I then again read the help and then I foung the
.pdb file reference.Then I searched the .pdb files in my project and I
found a handful .pdb files. I placed them in seprate folder and included
that folder in in symbol file path along with the original symbol file
path(windows symbols directory) but I dont understand the image path. help
says that it is the path of the binary executables. Shall I place the .exe
file path that simulates my driver. And after this, I again restart the
target machine but all in vain. I can see the breakpoint list using the bl
command but the debugger doesn’t staop at that location. I can see my
debug messages at that location means that part is in the flow. Why it
doesnt break?
One more thing… I have seen pleanty of error messages at the time of
booting indicating that the module is loaded but the symbols are not
loaded in the <>.dll file.
I copied a dump of that :
*** ERROR: Module load completed but symbols could not be loaded for
atl.dll
*** ERROR: Module load completed but symbols could not be loaded for
ntlanman.dll
*** ERROR: Module load completed but symbols could not be loaded for
netui0.dll
*** ERROR: Module load completed but symbols could not be loaded for
netui1.dll
*** ERROR: Module load completed but symbols could not be loaded for
netshell.dll
*** ERROR: Module load completed but symbols could not be loaded for
webcheck.dll
*** ERROR: Module load completed but symbols could not be loaded for
stobject.dll
*** ERROR: Module load completed but symbols could not be loaded for
batmeter.dll
*** ERROR: Module load completed but symbols could not be loaded for
msi.dll
*** WARNING: symbols timestamp is wrong 0x39cab2b9 0x37f5494c for
mobsync.exe
*** ERROR: Module load completed but symbols could not be loaded for
mobsync.exe
*** ERROR: Module load completed but symbols could not be loaded for
mobsync.dll
*** ERROR: Module load completed but symbols could not be loaded for
netman.dll
Is this is creating problem in breakpoints? I am now really
confused.Please help me.Sorry For The Long Mail.But I really need help.
Anand.
P.s. : is there any use of the VC option of creating driver or debugging
driver?When I installed the WDM eBook, It has created one more option in
the VC project creation menu and that is WDM Driver Wizard. That wizard
creates a project that can be compiled. What next? Have anybody used that?
Hi,
Is the path in the source path field pointing to where the code
of the driver u r trying to debug present. If not add the path.
There’ll be a pdb for the binary which you are trying to debug, just
point the symbol path to that directory. Not too sure about the
image path, never used it.
You can have multiple entries, seperating them by a semicolon (
for both.
The error messages ur getting is because u don’t the symbols for
those modules, nothing to worry about unless u r trying to debug
some of those.
U can use VC for building (search for ddkbuild) but not for debugging.
Hope this helps,
Regards,
Rajiv.
-----Original Message-----
From: Anand [mailto:xxxxx@lambenttek.com]
Sent: Tuesday, August 06, 2002 11:47 AM
To: NT Developers Interest List
Subject: [ntdev] RE: assembly code at breakpoing.
Hello all,
I got ur point.I checked that source path field and found it is already
filled by the debugger.I then again read the help and then I foung the
.pdb file reference.Then I searched the .pdb files in my project and I
found a handful .pdb files. I placed them in seprate folder and included
that folder in in symbol file path along with the original symbol file
path(windows symbols directory) but I dont understand the image
path. help
says that it is the path of the binary executables. Shall I
place the .exe
file path that simulates my driver. And after this, I again restart the
target machine but all in vain. I can see the breakpoint list
using the bl
command but the debugger doesn’t staop at that location. I can see my
debug messages at that location means that part is in the flow. Why it
doesnt break?
One more thing… I have seen pleanty of error messages at the time of
booting indicating that the module is loaded but the symbols are not
loaded in the <>.dll file.
I copied a dump of that :
*** ERROR: Module load completed but symbols could not be loaded for
atl.dll
*** ERROR: Module load completed but symbols could not be loaded for
ntlanman.dll
*** ERROR: Module load completed but symbols could not be loaded for
netui0.dll
*** ERROR: Module load completed but symbols could not be loaded for
netui1.dll
*** ERROR: Module load completed but symbols could not be loaded for
netshell.dll
*** ERROR: Module load completed but symbols could not be loaded for
webcheck.dll
*** ERROR: Module load completed but symbols could not be loaded for
stobject.dll
*** ERROR: Module load completed but symbols could not be loaded for
batmeter.dll
*** ERROR: Module load completed but symbols could not be loaded for
msi.dll
*** WARNING: symbols timestamp is wrong 0x39cab2b9 0x37f5494c for
mobsync.exe
*** ERROR: Module load completed but symbols could not be loaded for
mobsync.exe
*** ERROR: Module load completed but symbols could not be loaded for
mobsync.dll
*** ERROR: Module load completed but symbols could not be loaded for
netman.dll
Is this is creating problem in breakpoints? I am now really
confused.Please help me.Sorry For The Long Mail.But I really need help.
Anand.
P.s. : is there any use of the VC option of creating driver or debugging
driver?When I installed the WDM eBook, It has created one more option in
the VC project creation menu and that is WDM Driver Wizard. That wizard
creates a project that can be compiled. What next? Have anybody
used that?
You are currently subscribed to ntdev as: xxxxx@wipro.com
To unsubscribe send a blank email to %%email.unsub%%
Your symbols are screwed and thus the debugger can’t relate your source.
Fix your symbol path and it should help. Make sure you have the path to the
PDB for your driver in there as well as the path to the OS symbols. I would
highly recommend using the symbol server as explained here:
http://www.microsoft.com/ddk/debugging/symbols.asp
–
Bill McKenzie
Windows DDK MVP
OSR - Windows System Software Development, Training, and Consulting
“Anand” wrote in message news:xxxxx@ntdev…
>
> Hello all,
> I got ur point.I checked that source path field and found it is already
> filled by the debugger.I then again read the help and then I foung the
> .pdb file reference.Then I searched the .pdb files in my project and I
> found a handful .pdb files. I placed them in seprate folder and included
> that folder in in symbol file path along with the original symbol file
> path(windows symbols directory) but I dont understand the image path. help
> says that it is the path of the binary executables. Shall I place the .exe
> file path that simulates my driver. And after this, I again restart the
> target machine but all in vain. I can see the breakpoint list using the bl
> command but the debugger doesn’t staop at that location. I can see my
> debug messages at that location means that part is in the flow. Why it
> doesnt break?
> One more thing… I have seen pleanty of error messages at the time of
> booting indicating that the module is loaded but the symbols are not
> loaded in the <>.dll file.
> I copied a dump of that :
>
> ERROR: Module load completed but symbols could not be loaded for
> atl.dll
> ERROR: Module load completed but symbols could not be loaded for
> ntlanman.dll
> ERROR: Module load completed but symbols could not be loaded for
> netui0.dll
> ERROR: Module load completed but symbols could not be loaded for
> netui1.dll
> ERROR: Module load completed but symbols could not be loaded for
> netshell.dll
> ERROR: Module load completed but symbols could not be loaded for
> webcheck.dll
> ERROR: Module load completed but symbols could not be loaded for
> stobject.dll
> ERROR: Module load completed but symbols could not be loaded for
> batmeter.dll
> ERROR: Module load completed but symbols could not be loaded for
> msi.dll
> WARNING: symbols timestamp is wrong 0x39cab2b9 0x37f5494c for
> mobsync.exe
> ERROR: Module load completed but symbols could not be loaded for
> mobsync.exe
> ERROR: Module load completed but symbols could not be loaded for
> mobsync.dll
> *** ERROR: Module load completed but symbols could not be loaded for
> netman.dll
>
> Is this is creating problem in breakpoints? I am now really
> confused.Please help me.Sorry For The Long Mail.But I really need help.
> Anand.
> P.s. : is there any use of the VC option of creating driver or debugging
> driver?When I installed the WDM eBook, It has created one more option in
> the VC project creation menu and that is WDM Driver Wizard. That wizard
> creates a project that can be compiled. What next? Have anybody used that?
>
>
Hi,
if you are using DbgBreakPoint any other like function then it will break you in the ntoskernal code. If this is the scenerio then you have two options:
- check the function’s stack and go step up until you come up in your code.
- use int 3 to set break point.
Hope it will help you.
Best Regards,
Dav
“Rajiv B.L.” wrote:Hi,
Have you set the source file path in the debugger?
Regards,
Rajiv.
-----Original Message-----
From: Anand [mailto:xxxxx@lambenttek.com]
Sent: Tuesday, August 06, 2002 10:14 AM
To: NT Developers Interest List
Subject: [ntdev] assembly code at breakpoing.
I am debugging the dus driver for the first time.Now I am able
to apply a
breakpoint in a file . But when the flow comes at the
breakpoint, it gives
the control in my hand but the source code I see on debugger is
ASEMBLEY.BUt I want the source code to debug.I got to know that there is
special option in the build command.I tried to search it but I
didn’t see
any such option. I have gave the build -ceZ option. So can u
tell me that
option?I am using windbg 6 now.
Anand.
You are currently subscribed to ntdev as: xxxxx@wipro.com
To unsubscribe send a blank email to %%email.unsub%%
You are currently subscribed to ntdev as: xxxxx@yahoo.com
To unsubscribe send a blank email to %%email.unsub%%
Do You Yahoo!?
HotJobs, a Yahoo! service - Search Thousands of New Jobs