Yes, Source mode is ON. Symbols should be okay. I got them from the
customer’s diagnostics CD, and I don’t get any error from WinDbg about
symbols. Can you describe your procedure to enable source debugging. I tell
you how my system is set-up:
Symbols dir: c:\myprojects\tcpip\tcp\obj\i386;C:\W2000SYM\checked\Symbols
Source dir: c:\myprojects\tcpip\tcp
Image dir: c:\myprojects\tcpip\tcp\obj\i386
I set these paths in WinDbg using .sympath, .srcpath, etc…
I wish to debug the UDPSend function in the located in the source file udp.c
Now here’s my procedure:
- turn on the target machine
- connect WinDbg and set path parameters
- load source file (udp.c) using LSF command
- Source mode is on
if i set a breakpoint on tcpip!UDPSend the system breaks whenever i try to
send a UDP packet but no source debugging is done. If i set a breakpoint
indicatig sourcefile:lineno the system doesn’t break.
Notice that i replaced the standard tcpip.sys driver of Win2000 with my own.
Could this affect something ?
Thanks ALOT !!!
Matteo
----- Original Message -----
From: “Miguel Monteiro”
To: “NT Developers Interest List”
Sent: Tuesday, April 10, 2001 3:44 PM
Subject: [ntdev] Re: Windbg warning
> You wrote:
> >I’m unable to do source debugging [using] WinDbg (…)
>
> On WinDbg, did you turned Source Mode ON? 
> I dunno what else might be wrong, except that you might
> be using wrong symbols…
>
> Sorry (hope it helps anyway),
>
> Miguel Monteiro
> xxxxx@criticalsoftware.com
> www.criticalsoftware.com
> ------------------------------------------------------------
> «Humour and love are God’s answers
> to Human weaknesses»
> ------------------------------------------------------------
>
> ----- Original Message -----
> From: “Matteo Pelati”
> To: “NT Developers Interest List”
> Sent: Tuesday, April 10, 2001 12:35 PM
> Subject: [ntdev] Re: Windbg warning
>
>
> Thanks. In fact those are the seetings I’m currently using…but no
> way…
>
> Matteo
>
> ----- Original Message -----
> From: “Miguel Monteiro”
> To: “NT Developers Interest List”
> Sent: Tuesday, April 10, 2001 12:15 PM
> Subject: [ntdev] Re: Windbg warning
>
>
> > The image path should point to where your executable image is located.
> > Usually, paths are relative to your development (host) machine;
> however,
> > you debug and set breakpoints by running your apps/drivers on the
> > target machine.You may also use _NT_xxx environment variables - e.g.,
> > assuming you have Win2K SP1 symbols installed on C:\WINNT\Symbols
> > (on host) and you’re developing a driver on C:\MyProjects\MyDriver,
> you
> > could use:
> >
> > _NT_ALT_SYMBOL_PATH=C:\WINNT\Symbols
> > _NT_EXECUTABLE_IMAGE_PATH=C:\MyProjects\MyDriver\i386\sys
> > _NT_SYMBOL_PATH=C:\MyProjects\MyDriver\i386\sys
> > _NT_SOURCE_PATH=C:\MyProjects\MyDriver
> >
> > Check the DDK documentation for detailed information on setting paths
> > and symbols.
> >
> > Hope it helps,
> >
> > Miguel Monteiro
> > xxxxx@criticalsoftware.com
> > www.criticalsoftware.com
> > ------------------------------------------------------------
> > «Humour and love are God’s answers
> > to Human weaknesses»
> > ------------------------------------------------------------
> >
> > ----- Original Message -----
> > From: “Matteo Pelati”
> > To: “NT Developers Interest List”
> > Sent: Tuesday, April 10, 2001 10:02 AM
> > Subject: [ntdev] Re: Windbg warning
> >
> >
> > I’m running the WinDbg on my W200 Server SP1 (free) and the target
> > machine
> > is a W2000 Pro (Checked). Where the image path should point to ?
> >
> > Thanks
> > Matteo
> >
> > ----- Original Message -----
> > From: “Miguel Monteiro”
> > To: “NT Developers Interest List”
> > Sent: Tuesday, April 10, 2001 10:27 AM
> > Subject: [ntdev] Re: Windbg warning
> >
> >
> > > On Tuesday, April 10, 2001 9:12 AM “Matteo Pelati” wrote:
> > >
> > > >I’m unable to do source debugging win WinDbg. Once my file
> > > >is loaded if i set a breakpoint with the command bp ‘filename:line’
> > > >the breakpoint is ignored, and if I set it using the
> > > modulename!function
> > > >the target system breaks but the disassembled vode is shown instead
> > > >of my c source file.
> > >
> > > First, check that the symbol path (Ctrl+S), image path (Ctrl+I) and
> > > source
> > > path (Ctrl+P) are correct; save the workspace, open your c source
> file
> > > and try again. Remember that to set a breakpoint, code must be
> present
> > > in memory (for e.g. if you’re debugging a device driver which is
> > > launched
> > > by a test app, only when the driver is present at memory you’re
> > allowed
> > > to
> > > set a breakpoint into it and relate it to its source).
> > >
> > > >I get a Warning from WinDbg saying it’s unable to check timestamp
> of
> > > >different modules. Could be that related to the source debigging
> > > problem
> > > >I’m having.
> > >
> > > Perhaps. Those invalid timestamp warnings appear frequently as a
> > WinDbg
> > > “feature” 
and usually it’s safe to ignore them. However, do not
> > > ignore
> > > warnings about invalid/missing symbols…
> > >
> > > Hope it helps,
> > >
> > > Miguel Monteiro
> > > xxxxx@criticalsoftware.com
> > > www.criticalsoftware.com
> > > ------------------------------------------------------------
> > > «Humour and love are God’s answers
> > > to Human weaknesses»
> > > ------------------------------------------------------------
> > >
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@dolce.it
> > > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
> >
> > —
> > You are currently subscribed to ntdev as:
> xxxxx@criticalsoftware.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@dolce.it
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@criticalsoftware.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@dolce.it
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com