Denis
Wed Jun 29 19:28:37 CDT 2005
Thanks.
I did build at the same place and everything though.
Denis
"James Antognini [MSFT]" <jantogni@online.microsoft.com> wrote in message
news:%23DRZzfQfFHA.268@TK2MSFTNGP15.phx.gbl...
> First, I think you're using an old debugger. Get the latest from
>
http://www.microsoft.com/whdc/devtools/debugging/default.mspx. That may fix
> your problem with !sym.
>
> Second, if you've not rebuilt your driver and have its source code in the
> same place as what you used for the current build, you should see your
> source without further ado. That is because the driver executable contains
> information about where, and when, it was built.
>
> --
> James Antognini
> Windows DDK Support
>
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
> "Denis @ TheOffice" <denisco@ica.net> wrote in message
> news:1120089642.408059@www.vif.com...
> > Thanks,
> > That is my gift... I always trigger the worst in software. it is very
> > painful...
> >
> > Debugger extension library [E:\NTDDK\bin\W2KFre\kdextx86] loaded
> > E:\NTDDK\bin\W2KFre\kdextx86 uses the old 32 bit extension API and may not
> > be fully
> > compatible with current systems.
> > Missing extension: 'E:\NTDDK\bin\W2KFre\kdextx86.sym'
> > Could not find extension: 'sym'
> >> !sym noisy
> >
> > I don't see my source in-there???
> > Although, I see previously that it kind of loaded but I still can't trace
> > in my sources.
> >
> > Break, Ignore, Terminate Process or Terminate Thread (bipt)? b
> > Execute '!cxr EB83B76C' to dump context
> > Hard coded breakpoint hit
> > D:\Docuport\Docupen\Wideusb.003\sys\objchk\i386\WideUsb.sys for
> > WIDEUSB.SYS (symbols loaded)
> > Module Load: D:\Docuport\Docupen\Wideusb.003\sys\objchk\i386\WideUsb.pdb
> > (symbols loaded)
> >
> >
> > Denis
> >
> > "Don Burn" <burn@stopspam.acm.org> wrote in message
> > news:TKFwe.1990$394.738@fe07.lga...
> >> Lets see I've been doing this for 10 years now with rarely a problem.
> >> First
> >> the best places to ask windbg questions are either the
> >> microsoft.public.windbg newsgroup or the windbg group at
> >>
http://www.osronline.com/ the developers for WinDBG hang out on both of
> >> them. Try using "!sym noisy: to see if your symbols are correct.
> >>
> >>
> >> --
> >> Don Burn (MVP, Windows DDK)
> >> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> >> Remove StopSpam from the email to reply
> >>
> >>
> >>
> >> "Denis @ TheOffice" <denisco@ica.net> wrote in message
> >> news:1120084706.393899@www.vif.com...
> >> > Does someone has successfully debug with source and break point and all
> >> > with the WinDbg?
> >> >
> >> > I put a break point in my source code... (set the source path and all)
> >> > When my driver loads it always tell me that it cannot locate the
> >> > breakpoint???
> >> >
> >> >
> >> > Thanks
> >> > Denis
> >> >
> >> >
> >>
> >>
> >
> >
> >
>
>