Hello
I have written a USB device driver that works on W2K and XP.
The driver is written using Windows DDK 3790.1830 and Visual Studio.NET .
It crashes when installed on Vista.
I installed the latest Windbg and set a serial connection to the Vista target.
My host is running W2K.
I setup the symbol/target path to where the .PDB and .SYS files reside, and
the source path to where my .C files reside.
The debugger connects to the target, but when I try to set a break point, the
debugger cannot find the symbols that matches the requested line.
I turned on ‘noisy symbol loading’ and verified the debugger search path to be OK.
Once the target crashes and I check the call stack, I see my driver there and the stack points to logical locations within my driver as if the symbols match.
When I try to reload my driver’s symbols before it is loaded to target memory, windbg fails
to locate the module/symbols.
Does any body has a clue what am I doing wrong.
Thanks
Asher
If you do this with !sym noisy', what output do you get? Usually, usage of the !sym nosiy’ command is the best way to troubleshoot symbol load
failures.
–
Ken Johnson (Skywing)
Windows SDK MVP
http://www.nynaeve.net
“Asher Kariv” wrote in message
news:xxxxx@windbg…
> Hello
>
> I have written a USB device driver that works on W2K and XP.
> The driver is written using Windows DDK 3790.1830 and Visual Studio.NET .
> It crashes when installed on Vista.
> I installed the latest Windbg and set a serial connection to the Vista
> target.
> My host is running W2K.
> I setup the symbol/target path to where the .PDB and .SYS files reside,
> and
> the source path to where my .C files reside.
> The debugger connects to the target, but when I try to set a break point,
> the
> debugger cannot find the symbols that matches the requested line.
> I turned on ‘noisy symbol loading’ and verified the debugger search path
> to be OK.
> Once the target crashes and I check the call stack, I see my driver there
> and the stack points to logical locations within my driver as if the
> symbols match.
> When I try to reload my driver’s symbols before it is loaded to target
> memory, windbg fails
> to locate the module/symbols.
>
> Does any body has a clue what am I doing wrong.
>
> Thanks
>
> Asher
>
>