Symbol Errors

Hi all,

Previously, I posted a message that I cannot see
a the C source.
While attempting to solve this problem, I noticed
that windbg seems to complain about my symbols.
I would greatly appreciate if someone could tell me
if it’s the below output is the usual behaviour of
windbg ?

( my .sympath and .srcpath are both set, I also
tried to specify “.reload serialdrv.sys” as well
as full path to the file, but I got same results as
the below, I build the driver using the checked
build environment.)

---------WINDBG OUTPUT-------------------
kd> .reload serialdrv.pdb

Module “serialdrv.pdb” was not found in the module
list.
Debugger will attempt to load module “serialdrv.pdb”
by guessing the base address.
Please provide the full image name, including the
extension (i.e. kernel32.dll) for more reliable
results.
DBGHELP: .\serialdrv.pdb - file not found.

DBGHELP: Can’t use symbol server for serialdrv.pdb -
no header information available.

DBGHELP:
e:\projects\serialdrv\objchk\i386\symbols\exe\serialdrv.pdb

  • file not found.

DBGHELP:
e:\projects\serialdrv\objchk\i386\exe\serialdrv.pdb -
file not found.

?***? DBGHELP:
e:\projects\serialdrv\objchk\i386\serialdrv.pdb -
unknown pdb sig opened.

?***?DBGHELP: No base address for serialdrv.pdb:
Please specify Unable to load module at 00000000

Thanks,
Mike.


Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!
http://greetings.yahoo.com

Hi,
Firstly you are telling the debugger to load symbols for ‘serialdrv.pdb’ and
it correctly says serialdrv.pdb so not a loaded module, you should use
‘.reload serialdrv.sys’.

Also I always use the ‘/f’ option when using .reload otherwiae WinDbg may
decide not to load them.
So use :

.reload serialdrv.sys /f

Yours
Roger


Roger Coote,
Senior Design Engineer
PowerVR Technologies, A Division of Imagination Technologies Ltd
Home Park Estate, Kings Langley, Hertfordshire, WD4 8LZ, UK
phone :+44 (1923) 260511 fax :+44 (1923) 268969
direct :+44 (1923) 277274
mailto:xxxxx@powervr.com www.powervr.com


-----Original Message-----
From: Mike Malgin [mailto:xxxxx@yahoo.com]
Sent: 28 February 2002 17:45
To: Kernel Debugging Interest List
Subject: [windbg] Symbol Errors

Hi all,

Previously, I posted a message that I cannot see
a the C source.
While attempting to solve this problem, I noticed
that windbg seems to complain about my symbols.
I would greatly appreciate if someone could tell me
if it’s the below output is the usual behaviour of
windbg ?

( my .sympath and .srcpath are both set, I also
tried to specify “.reload serialdrv.sys” as well
as full path to the file, but I got same results as
the below, I build the driver using the checked
build environment.)

---------WINDBG OUTPUT-------------------
kd> .reload serialdrv.pdb

Module “serialdrv.pdb” was not found in the module
list.
Debugger will attempt to load module “serialdrv.pdb”
by guessing the base address.
Please provide the full image name, including the
extension (i.e. kernel32.dll) for more reliable
results.
DBGHELP: .\serialdrv.pdb - file not found.

DBGHELP: Can’t use symbol server for serialdrv.pdb -
no header information available.

DBGHELP:
e:\projects\serialdrv\objchk\i386\symbols\exe\serialdrv.pdb

  • file not found.

DBGHELP:
e:\projects\serialdrv\objchk\i386\exe\serialdrv.pdb -
file not found.

?***? DBGHELP:
e:\projects\serialdrv\objchk\i386\serialdrv.pdb -
unknown pdb sig opened.

?***?DBGHELP: No base address for serialdrv.pdb:
Please specify Unable to load module at 00000000

Thanks,
Mike.


Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!
http://greetings.yahoo.com


You are currently subscribed to windbg as: xxxxx@videologic.com
To unsubscribe send a blank email to %%email.unsub%%

Hi,

I also tried to specify “serialdrv.sys”, but I get
similar results…

kd> .reload /f serialdrv.sys

?***? DBGHELP: serialdrv.sys missing debug info.
Searching for pdb anyway.

DBGHELP: Can’t use symbol server for serialdrv.pdb -
no header information available.

DBGHELP:
e:\projects\serialdrv\objchk\i386\symbols\SYS\serialdrv.pdb

  • file not found.

DBGHELP:
e:\projects\serialdrv\objchk\i386\SYS\serialdrv.pdb -
file not found.

?***? DBGHELP:
e:\projects\serialdrv\objchk\i386\serialdrv.pdb -
unknown pdb sig opened.

DBGHELP: C:\Program Files\Debugging Tools for
Windows\serialdrv.sys - file not found.

DBGHELP:
f:\projects\serialdrv\objchk\i386\serialdrv.sys -
mismatched timestamp

?**?DBGHELP: serialdrv.sys not found in
e:\projects\serialdrv\objchk\i386.

DBGHELP: serialdrv - private symbols -
e:\projects\serialdrv\objchk\i386\serialdrv.pdb.

Thanks,
Mike.

— Roger Coote wrote:
> Hi,
> Firstly you are telling the debugger to load symbols
> for ‘serialdrv.pdb’ and
> it correctly says serialdrv.pdb so not a loaded
> module, you should use
> ‘.reload serialdrv.sys’.
>
> Also I always use the ‘/f’ option when using .reload
> otherwiae WinDbg may
> decide not to load them.
> So use :
>
> .reload serialdrv.sys /f
>
> Yours
> Roger
>

> Roger Coote,
> Senior Design Engineer
> PowerVR Technologies, A Division of Imagination
> Technologies Ltd
> Home Park Estate, Kings Langley, Hertfordshire,
> WD4 8LZ, UK
> phone :+44 (1923) 260511 fax :+44
> (1923) 268969
> direct :+44 (1923) 277274
> mailto:xxxxx@powervr.com www.powervr.com
>

>
>
>
> -----Original Message-----
> From: Mike Malgin [mailto:xxxxx@yahoo.com]
> Sent: 28 February 2002 17:45
> To: Kernel Debugging Interest List
> Subject: [windbg] Symbol Errors
>
>
> Hi all,
>
> Previously, I posted a message that I cannot see
> a the C source.
> While attempting to solve this problem, I noticed
> that windbg seems to complain about my symbols.
> I would greatly appreciate if someone could tell me
>
> if it’s the below output is the usual behaviour of
> windbg ?
>
> ( my .sympath and .srcpath are both set, I also
> tried to specify “.reload serialdrv.sys” as well
> as full path to the file, but I got same results
> as
> the below, I build the driver using the checked
> build environment.)
>
> ---------WINDBG OUTPUT-------------------
> kd> .reload serialdrv.pdb
>
> Module “serialdrv.pdb” was not found in the module
> list.
> Debugger will attempt to load module “serialdrv.pdb”
> by guessing the base address.
> Please provide the full image name, including the
> extension (i.e. kernel32.dll) for more reliable
> results.
> DBGHELP: .\serialdrv.pdb - file not found.
>
> DBGHELP: Can’t use symbol server for serialdrv.pdb -
>
> no header information available.
>
> DBGHELP:
>
e:\projects\serialdrv\objchk\i386\symbols\exe\serialdrv.pdb
> - file not found.
>
> DBGHELP:
> e:\projects\serialdrv\objchk\i386\exe\serialdrv.pdb
> -
> file not found.
>
> ? ? DBGHELP:
> e:\projects\serialdrv\objchk\i386\serialdrv.pdb -
> unknown pdb sig opened.
>
> ?
?DBGHELP: No base address for serialdrv.pdb:
> Please specify Unable to load module at 00000000
> ---------------------------------------------
>
> Thanks,
> Mike.
>
>
> Do You Yahoo!?
> Yahoo! Greetings - Send FREE e-cards for every
> occasion!
> http://greetings.yahoo.com
>
> —
> You are currently subscribed to windbg as:
> xxxxx@videologic.com
> To unsubscribe send a blank email to %%email.unsub%%
>
> —
> You are currently subscribed to windbg as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
%%email.unsub%%


Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!
http://greetings.yahoo.com

Do you have your build environment setup to *produce* serialdrv.pdb? After
a successful build, does:
dir /s e:\projects\serialdrv*.pdb
find at least one file?
I suspect that the answer is no, and if that is the case, the easiest way
to correct that is to put
USE_PDB=1 into your SOURCES file.

Hope this helps,

Phil

Mike Malgin @lists.osr.com on 02/28/2002 11:26:56 AM

Please respond to “Kernel Debugging Interest List”

Sent by: xxxxx@lists.osr.com

To: “Kernel Debugging Interest List”
cc:

Subject: [windbg] RE: Symbol Errors

Hi,

I also tried to specify “serialdrv.sys”, but I get
similar results…

kd> .reload /f serialdrv.sys

? ? DBGHELP: serialdrv.sys missing debug info.
Searching for pdb anyway.

DBGHELP: Can’t use symbol server for serialdrv.pdb -
no header information available.

DBGHELP:
e:\projects\serialdrv\objchk\i386\symbols\SYS\serialdrv.pdb
- file not found.

DBGHELP:
e:\projects\serialdrv\objchk\i386\SYS\serialdrv.pdb -
file not found.

?
? DBGHELP:
e:\projects\serialdrv\objchk\i386\serialdrv.pdb -
unknown pdb sig opened.

DBGHELP: C:\Program Files\Debugging Tools for
Windows\serialdrv.sys - file not found.

DBGHELP:
f:\projects\serialdrv\objchk\i386\serialdrv.sys -
mismatched timestamp

?**?DBGHELP: serialdrv.sys not found in
e:\projects\serialdrv\objchk\i386.

DBGHELP: serialdrv - private symbols -
e:\projects\serialdrv\objchk\i386\serialdrv.pdb.

Oh, poop. I should read a bit more carefully before I display my
carelessness for all the world to see.

This:
?***? DBGHELP:
e:\projects\serialdrv\objchk\i386\serialdrv.pdb -
unknown pdb sig opened.

DBGHELP: C:\Program Files\Debugging Tools for
Windows\serialdrv.sys - file not found.

DBGHELP:
f:\projects\serialdrv\objchk\i386\serialdrv.sys -
mismatched timestamp
means that it found a PDB, but it doesn’t match the driver image on your
target system. Rebuild your driver, making sure that both the .sys and
.pdb files are updated. Then load your driver on the target, and that
*should* fix the problem.

Phil

xxxxx@xxxxx@lists.osr.com on 02/28/2002 12:13:25 PM

Please respond to “Kernel Debugging Interest List”

Sent by: xxxxx@lists.osr.com

To: “Kernel Debugging Interest List”
cc:

Subject: [windbg] RE: Symbol Errors

Do you have your build environment setup to produce serialdrv.pdb? After
a successful build, does:
dir /s e:\projects\serialdrv*.pdb
find at least one file?
I suspect that the answer is no, and if that is the case, the easiest way
to correct that is to put
USE_PDB=1 into your SOURCES file.

Hope this helps,

Phil

Mike Malgin @lists.osr.com on 02/28/2002 11:26:56 AM

Please respond to “Kernel Debugging Interest List”

Sent by: xxxxx@lists.osr.com

To: “Kernel Debugging Interest List”
cc:

Subject: [windbg] RE: Symbol Errors

Hi,

I also tried to specify “serialdrv.sys”, but I get
similar results…

kd> .reload /f serialdrv.sys

? ? DBGHELP: serialdrv.sys missing debug info.
Searching for pdb anyway.

DBGHELP: Can’t use symbol server for serialdrv.pdb -
no header information available.

DBGHELP:
e:\projects\serialdrv\objchk\i386\symbols\SYS\serialdrv.pdb
- file not found.

DBGHELP:
e:\projects\serialdrv\objchk\i386\SYS\serialdrv.pdb -
file not found.

?
? DBGHELP:
e:\projects\serialdrv\objchk\i386\serialdrv.pdb -
unknown pdb sig opened.

DBGHELP: C:\Program Files\Debugging Tools for
Windows\serialdrv.sys - file not found.

DBGHELP:
f:\projects\serialdrv\objchk\i386\serialdrv.sys -
mismatched timestamp

?**?DBGHELP: serialdrv.sys not found in
e:\projects\serialdrv\objchk\i386.

DBGHELP: serialdrv - private symbols -
e:\projects\serialdrv\objchk\i386\serialdrv.pdb.


You are currently subscribed to windbg as: xxxxx@seagate.com
To unsubscribe send a blank email to %%email.unsub%%

Hi Philip,

You were right, that is, the versions of the pdb
didn’t correspond to the sys, thanks!.

However, I still get the following error
“e:\projects\serialdrv\objchk\i386\serialdrv.pdb -
unknown pdb sig opened.”
(I also used your suggestion and included
USE_PDB = 1 in the SOURCE file )
I was wondering if someone know how to stamp out
this error(or whatever it is) ?

When WinDbg is break on the bp it still come
up with the asm listing instead of C, I guess the
above error has to do with that ?

Thank you!
-Mike.

xxxxx@seagate.com wrote:

Oh, poop. I should read a bit more carefully before
I display my
carelessness for all the world to see.

This:
?***? DBGHELP:
e:\projects\serialdrv\objchk\i386\serialdrv.pdb -
unknown pdb sig opened.

DBGHELP: C:\Program Files\Debugging Tools for
Windows\serialdrv.sys - file not found.

DBGHELP:
f:\projects\serialdrv\objchk\i386\serialdrv.sys -
mismatched timestamp
means that it found a PDB, but it doesn’t match the
driver image on your
target system. Rebuild your driver, making sure
that both the .sys and
.pdb files are updated. Then load your driver on
the target, and that
*should* fix the problem.

Phil

xxxxx@xxxxx@lists.osr.com on
02/28/2002 12:13:25 PM

Please respond to “Kernel Debugging Interest List”

>
> Sent by: xxxxx@lists.osr.com
>
>
> To: “Kernel Debugging Interest List”
>
> cc:
>
> Subject: [windbg] RE: Symbol Errors
>
>
>
> Do you have your build environment setup to
> produce serialdrv.pdb? After
> a successful build, does:
> dir /s e:\projects\serialdrv*.pdb
> find at least one file?
> I suspect that the answer is no, and if that is the
> case, the easiest way
> to correct that is to put
> USE_PDB=1 into your SOURCES file.
>
> Hope this helps,
>
> Phil
>
>
>
>
>
> Mike Malgin @lists.osr.com on
> 02/28/2002 11:26:56 AM
>
> Please respond to “Kernel Debugging Interest List”
>
>
> Sent by: xxxxx@lists.osr.com
>
>
> To: “Kernel Debugging Interest List”
>
> cc:
>
> Subject: [windbg] RE: Symbol Errors
>
>
> Hi,
>
> I also tried to specify “serialdrv.sys”, but I get
> similar results…
>
> kd> .reload /f serialdrv.sys
>
> ? ? DBGHELP: serialdrv.sys missing debug info.
> Searching for pdb anyway.
>
> DBGHELP: Can’t use symbol server for serialdrv.pdb -
> no header information available.
>
> DBGHELP:
>
e:\projects\serialdrv\objchk\i386\symbols\SYS\serialdrv.pdb
> - file not found.
>
> DBGHELP:
> e:\projects\serialdrv\objchk\i386\SYS\serialdrv.pdb
> -
> file not found.
>
> ?
? DBGHELP:
> e:\projects\serialdrv\objchk\i386\serialdrv.pdb -
> unknown pdb sig opened.
>
> DBGHELP: C:\Program Files\Debugging Tools for
> Windows\serialdrv.sys - file not found.
>
> DBGHELP:
> f:\projects\serialdrv\objchk\i386\serialdrv.sys -
> mismatched timestamp
>
> ?**?DBGHELP: serialdrv.sys not found in
> e:\projects\serialdrv\objchk\i386.
>
> DBGHELP: serialdrv - private symbols -
> e:\projects\serialdrv\objchk\i386\serialdrv.pdb.
>
>
>
> —
> You are currently subscribed to windbg as:
> xxxxx@seagate.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
>
>
> —
> You are currently subscribed to windbg as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
%%email.unsub%%

__________________________________________________
Do You Yahoo!?
Yahoo! Sports - sign up for Fantasy Baseball
http://sports.yahoo.com

Mike,

I’mn not sure, but it might have to do with the fact that it looks like you
have stuff spread all over the place. As I reread all the quoted stuff
(which I have snipped for the benefit of the digest readers), I noticed
that your pdb is coming from drive E:, but your .sys is coming from drive
F:

I’ve had really good success with the following setup, maybe if you try to
duplicate it, it might reduce the trouble you are having.

Driver directory on a local disk, say D:\Projects\serialdrv for this
discussion.

In order to simplify supporting multiple target OS’es, a symbol store in:
d:\program files\debugging tools for windows\symstore (It can be
anywhere, really)

Sympath set to:
D:\Projects\serialdrv;srv*d:\program files\debugging tools for
windows\symstore*http://msdl.microsoft.com/download/symbols

No executable or source search path, as that can confuse things more than
they help.

Make sure the Debug->Source Mode menu item has a big check mark to the left
of it.

Build the driver, copy the binary directly to the install directory on the
target, wherever that might be. Since I was doing a boot disk driver, that
was usually a floppy so I could install it in place of ATAPI.sys.

Install the driver.

Start the 'Bag and set it up for kernel mode with the above setup. Cycle
the Initial Breakpoint until the command window says:
Will request initial breakpoint at next boot.

Restart the target.

At the initial breakpoint, you should be able to type into the command
line:
bp serialdrv!DriverEntry
and the breakpoint should set.

If your PDB and source files haven’t been moved, you should then be able to
tell it to run, it will run to your Driver Entry, and stop on the first
line in it.

Hope this works for you,

Phil

Mike Malgin @lists.osr.com on 03/02/2002 06:53:45 AM

Please respond to “Kernel Debugging Interest List”

Sent by: xxxxx@lists.osr.com

To: “Kernel Debugging Interest List”
cc:

Subject: [windbg] RE: Symbol Errors

Hi Philip,

You were right, that is, the versions of the pdb
didn’t correspond to the sys, thanks!.

However, I still get the following error
“e:\projects\serialdrv\objchk\i386\serialdrv.pdb -
unknown pdb sig opened.”
(I also used your suggestion and included
USE_PDB = 1 in the SOURCE file )
I was wondering if someone know how to stamp out
this error(or whatever it is) ?

When WinDbg is break on the bp it still come
up with the asm listing instead of C, I guess the
above error has to do with that ?

Thank you!
-Mike.


You are currently subscribed to windbg as: xxxxx@seagate.com
To unsubscribe send a blank email to %%email.unsub%%

Hi Philip,

I almost sure I did as you described in the below.
However, I will try to do it all over again
with the help of your description.

Thanks a lot!!

-Mike.

xxxxx@seagate.com wrote:

Mike,

I’mn not sure, but it might have to do with the fact
that it looks like you
have stuff spread all over the place. As I reread
all the quoted stuff
(which I have snipped for the benefit of the digest
readers), I noticed
that your pdb is coming from drive E:, but your .sys
is coming from drive
F:

I’ve had really good success with the following
setup, maybe if you try to
duplicate it, it might reduce the trouble you are
having.

Driver directory on a local disk, say
D:\Projects\serialdrv for this
discussion.

In order to simplify supporting multiple target
OS’es, a symbol store in:
d:\program files\debugging tools for
windows\symstore (It can be
anywhere, really)

Sympath set to:
D:\Projects\serialdrv;srv*d:\program files\debugging
tools for

windows\symstore*http://msdl.microsoft.com/download/symbols

No executable or source search path, as that can
confuse things more than
they help.

Make sure the Debug->Source Mode menu item has a big
check mark to the left
of it.

Build the driver, copy the binary directly to the
install directory on the
target, wherever that might be. Since I was doing a
boot disk driver, that
was usually a floppy so I could install it in place
of ATAPI.sys.

Install the driver.

Start the 'Bag and set it up for kernel mode with
the above setup. Cycle
the Initial Breakpoint until the command window
says:
Will request initial breakpoint at next boot.

Restart the target.

At the initial breakpoint, you should be able to
type into the command
line:
bp serialdrv!DriverEntry
and the breakpoint should set.

If your PDB and source files haven’t been moved, you
should then be able to
tell it to run, it will run to your Driver Entry,
and stop on the first
line in it.

Hope this works for you,

Phil

Mike Malgin @lists.osr.com on
> 03/02/2002 06:53:45 AM
>
> Please respond to “Kernel Debugging Interest List”
>
>
> Sent by: xxxxx@lists.osr.com
>
>
> To: “Kernel Debugging Interest List”
>
> cc:
>
> Subject: [windbg] RE: Symbol Errors
>
>
> Hi Philip,
>
> You were right, that is, the versions of the pdb
> didn’t correspond to the sys, thanks!.
>
> However, I still get the following error
> “e:\projects\serialdrv\objchk\i386\serialdrv.pdb -
> unknown pdb sig opened.”
> (I also used your suggestion and included
> USE_PDB = 1 in the SOURCE file )
> I was wondering if someone know how to stamp out
> this error(or whatever it is) ?
>
> When WinDbg is break on the bp it still come
> up with the asm listing instead of C, I guess the
> above error has to do with that ?
>
>
> Thank you!
> -Mike.
>
>
> —
> You are currently subscribed to windbg as:
> xxxxx@seagate.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
>
>
> —
> You are currently subscribed to windbg as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
%%email.unsub%%

__________________________________________________
Do You Yahoo!?
Yahoo! Sports - sign up for Fantasy Baseball
http://sports.yahoo.com

Hi,

Thanks the help.
Unfortunately, nothing seems to work,
so I guess I’m going to let it go for now.

Thanks,
-Mike.

— Mike Malgin wrote:
> Hi Philip,
>
> I almost sure I did as you described in the below.
> However, I will try to do it all over again
> with the help of your description.
>
> Thanks a lot!!
>
> -Mike.
>
> — xxxxx@seagate.com wrote:
> >
> > Mike,
> >
> > I’mn not sure, but it might have to do with the
> fact
> > that it looks like you
> > have stuff spread all over the place. As I reread
> > all the quoted stuff
> > (which I have snipped for the benefit of the
> digest
> > readers), I noticed
> > that your pdb is coming from drive E:, but your
> .sys
> > is coming from drive
> > F:
> >
> > I’ve had really good success with the following
> > setup, maybe if you try to
> > duplicate it, it might reduce the trouble you are
> > having.
> >
> > Driver directory on a local disk, say
> > D:\Projects\serialdrv for this
> > discussion.
> >
> > In order to simplify supporting multiple target
> > OS’es, a symbol store in:
> > d:\program files\debugging tools for
> > windows\symstore (It can be
> > anywhere, really)
> >
> > Sympath set to:
> > D:\Projects\serialdrv;srvd:\program
> files\debugging
> > tools for
> >
>
windows\symstore
http://msdl.microsoft.com/download/symbols
> >
> > No executable or source search path, as that can
> > confuse things more than
> > they help.
> >
> > Make sure the Debug->Source Mode menu item has a
> big
> > check mark to the left
> > of it.
> >
> > Build the driver, copy the binary directly to the
> > install directory on the
> > target, wherever that might be. Since I was doing
> a
> > boot disk driver, that
> > was usually a floppy so I could install it in
> place
> > of ATAPI.sys.
> >
> > Install the driver.
> >
> > Start the 'Bag and set it up for kernel mode with
> > the above setup. Cycle
> > the Initial Breakpoint until the command window
> > says:
> > Will request initial breakpoint at next boot.
> >
> > Restart the target.
> >
> > At the initial breakpoint, you should be able to
> > type into the command
> > line:
> > bp serialdrv!DriverEntry
> > and the breakpoint should set.
> >
> > If your PDB and source files haven’t been moved,
> you
> > should then be able to
> > tell it to run, it will run to your Driver Entry,
> > and stop on the first
> > line in it.
> >
> > Hope this works for you,
> >
> > Phil
> >
> >
> >
> >
> > Mike Malgin @lists.osr.com on
> > 03/02/2002 06:53:45 AM
> >
> > Please respond to “Kernel Debugging Interest List”
> >
> >
> > Sent by: xxxxx@lists.osr.com
> >
> >
> > To: “Kernel Debugging Interest List”
> >
> > cc:
> >
> > Subject: [windbg] RE: Symbol Errors
> >
> >
> > Hi Philip,
> >
> > You were right, that is, the versions of the pdb
> > didn’t correspond to the sys, thanks!.
> >
> > However, I still get the following error
> > “e:\projects\serialdrv\objchk\i386\serialdrv.pdb
> -
> > unknown pdb sig opened.”
> > (I also used your suggestion and included
> > USE_PDB = 1 in the SOURCE file )
> > I was wondering if someone know how to stamp out
> > this error(or whatever it is) ?
> >
> > When WinDbg is break on the bp it still come
> > up with the asm listing instead of C, I guess
> the
> > above error has to do with that ?
> >
> >
> > Thank you!
> > -Mike.
> >
> >
> > —
> > You are currently subscribed to windbg as:
> > xxxxx@seagate.com
> > To unsubscribe send a blank email to
> %%email.unsub%%
> >
> >
> >
> >
> > —
> > You are currently subscribed to windbg as:
> > xxxxx@yahoo.com
> > To unsubscribe send a blank email to
> %%email.unsub%%
>
>
>
> Do You Yahoo!?
> Yahoo! Sports - sign up for Fantasy Baseball
> http://sports.yahoo.com
>
> —
> You are currently subscribed to windbg as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
%%email.unsub%%


Do You Yahoo!?
Yahoo! Sports - sign up for Fantasy Baseball
http://sports.yahoo.com

What DDK are you using?

The unknown PDB is a big part of your problem, but I can’t think of any
reason other than you are using the wrong compiler or linker in your build
environment.

Anyone else have any suggestions why the 'Bag would complain about an
“unknown PDB”, as opposed to “mismatched timestamps”? Or is that the
current error message for mismatched symbols?

Phil

Mike Malgin @lists.osr.com on 03/04/2002 01:58:07 PM

Please respond to “Kernel Debugging Interest List”

Sent by: xxxxx@lists.osr.com

To: “Kernel Debugging Interest List”
cc:

Subject: [windbg] RE: Symbol Errors

Hi,

Thanks the help.
Unfortunately, nothing seems to work,
so I guess I’m going to let it go for now.

Thanks,
-Mike.

Hi Philip,

I’m using Windows 2000 DDK, the target is windows
2K Pro.

The weirdest thing is that when I look in the call
stack and click on my function a source window comes
up, the other thing is that when I do ‘lml’ to
verify the symbols I can actually see the name of the

driver and the path of the PDB file, which means
the symbols are ok ?! (i think).

On the other hand as you said I get “unknown sig
opened” every time when loading *MY driver PDB*
(even when doing according to your description)

Thanks,
-Mike.

xxxxx@seagate.com wrote:

What DDK are you using?

The unknown PDB is a big part of your problem, but I
can’t think of any
reason other than you are using the wrong compiler
or linker in your build
environment.

Anyone else have any suggestions why the 'Bag would
complain about an
“unknown PDB”, as opposed to “mismatched
timestamps”? Or is that the
current error message for mismatched symbols?

Phil

Mike Malgin @lists.osr.com on
> 03/04/2002 01:58:07 PM
>
> Please respond to “Kernel Debugging Interest List”
>
>
> Sent by: xxxxx@lists.osr.com
>
>
> To: “Kernel Debugging Interest List”
>
> cc:
>
> Subject: [windbg] RE: Symbol Errors
>
>
> Hi,
>
> Thanks the help.
> Unfortunately, nothing seems to work,
> so I guess I’m going to let it go for now.
>
> Thanks,
> -Mike.
>
>
>
>
> —
> You are currently subscribed to windbg as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
%%email.unsub%%

__________________________________________________
Do You Yahoo!?
Yahoo! Sports - sign up for Fantasy Baseball
http://sports.yahoo.com

I don’t know if you mentioned that you could open a source file from the
stack window before. Is the source file the correct one? Does it open to
the right statement? If you do that, can you single-step through your
code, set breakpoints, etc…?

If none of the above is correct, it’s possible that the PDB is corrupt
somehow. I don’t remember what combination of SOURCES macros I used, but I
do remember that I once caused build to produce PDBs that were very small,
without any useful information in them. The PDB should be some, maybe a
lot, bigger than your driver binary, and should have the fully qualified
filenames of your source files in it if you look at it in Notepad.

That might give you some ideas where to look…

Phil

Mike Malgin @lists.osr.com on 03/04/2002 02:36:52 PM

Please respond to “Kernel Debugging Interest List”

Sent by: xxxxx@lists.osr.com

To: “Kernel Debugging Interest List”
cc:

Subject: [windbg] RE: Symbol Errors

Hi Philip,

I’m using Windows 2000 DDK, the target is windows
2K Pro.

The weirdest thing is that when I look in the call
stack and click on my function a source window comes
up, the other thing is that when I do ‘lml’ to
verify the symbols I can actually see the name of the

driver and the path of the PDB file, which means
the symbols are ok ?! (i think).

On the other hand as you said I get “unknown sig
opened” every time when loading MY driver PDB
(even when doing according to your description)

Thanks,
-Mike.

xxxxx@seagate.com wrote:
>
> What DDK are you using?
>
> The unknown PDB is a big part of your problem, but I
> can’t think of any
> reason other than you are using the wrong compiler
> or linker in your build
> environment.
>
> Anyone else have any suggestions why the 'Bag would
> complain about an
> “unknown PDB”, as opposed to “mismatched
> timestamps”? Or is that the
> current error message for mismatched symbols?
>
> Phil
>
>
>
>
> Mike Malgin @lists.osr.com on
> 03/04/2002 01:58:07 PM
>
> Please respond to “Kernel Debugging Interest List”
>
>
> Sent by: xxxxx@lists.osr.com
>
>
> To: “Kernel Debugging Interest List”
>
> cc:
>
> Subject: [windbg] RE: Symbol Errors
>
>
> Hi,
>
> Thanks the help.
> Unfortunately, nothing seems to work,
> so I guess I’m going to let it go for now.
>
> Thanks,
> -Mike.
>
>
>
>
> —
> You are currently subscribed to windbg as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
%%email.unsub%%

__________________________________________________
Do You Yahoo!?
Yahoo! Sports - sign up for Fantasy Baseball
http://sports.yahoo.com


You are currently subscribed to windbg as: xxxxx@seagate.com
To unsubscribe send a blank email to %%email.unsub%%

Hi,

Yes, I’m able to do a single-step, setting bp is also
possible(I need to go back to the command window…
on break it shows asm listing),
the source seems to be correct and I’m also on the
right statment, but cannot do step-in etc.
The PDB file is about 400K larger then the sys file.

Despite the above, is this the way it should work?
I mean debugging through the local call stack?

Thanks!
-Mike.

xxxxx@seagate.com wrote:

I don’t know if you mentioned that you could open a
source file from the
stack window before. Is the source file the correct
one? Does it open to
the right statement? If you do that, can you
single-step through your
code, set breakpoints, etc…?

If none of the above is correct, it’s possible that
the PDB is corrupt
somehow. I don’t remember what combination of
SOURCES macros I used, but I
do remember that I once caused build to produce PDBs
that were very small,
without any useful information in them. The PDB
should be some, maybe a
lot, bigger than your driver binary, and should have
the fully qualified
filenames of your source files in it if you look at
it in Notepad.

That might give you some ideas where to look…

Phil

Mike Malgin @lists.osr.com on
> 03/04/2002 02:36:52 PM
>
> Please respond to “Kernel Debugging Interest List”
>
>
> Sent by: xxxxx@lists.osr.com
>
>
> To: “Kernel Debugging Interest List”
>
> cc:
>
> Subject: [windbg] RE: Symbol Errors
>
>
> Hi Philip,
>
> I’m using Windows 2000 DDK, the target is windows
> 2K Pro.
>
> The weirdest thing is that when I look in the call
> stack and click on my function a source window
> comes
> up, the other thing is that when I do ‘lml’ to
> verify the symbols I can actually see the name of
> the
>
> driver and the path of the PDB file, which means
> the symbols are ok ?! (i think).
>
> On the other hand as you said I get “unknown sig
> opened” every time when loading MY driver PDB
> (even when doing according to your description)
>
> Thanks,
> -Mike.
>
>
>
> — xxxxx@seagate.com wrote:
> >
> > What DDK are you using?
> >
> > The unknown PDB is a big part of your problem, but
> I
> > can’t think of any
> > reason other than you are using the wrong compiler
> > or linker in your build
> > environment.
> >
> > Anyone else have any suggestions why the 'Bag
> would
> > complain about an
> > “unknown PDB”, as opposed to “mismatched
> > timestamps”? Or is that the
> > current error message for mismatched symbols?
> >
> > Phil
> >
> >
> >
> >
> > Mike Malgin @lists.osr.com on
> > 03/04/2002 01:58:07 PM
> >
> > Please respond to “Kernel Debugging Interest List”
> >
> >
> > Sent by: xxxxx@lists.osr.com
> >
> >
> > To: “Kernel Debugging Interest List”
> >
> > cc:
> >
> > Subject: [windbg] RE: Symbol Errors
> >
> >
> > Hi,
> >
> > Thanks the help.
> > Unfortunately, nothing seems to work,
> > so I guess I’m going to let it go for now.
> >
> > Thanks,
> > -Mike.
> >
> >
> >
> >
> > —
> > You are currently subscribed to windbg as:
> > xxxxx@yahoo.com
> > To unsubscribe send a blank email to
> %%email.unsub%%
>
>
>
> Do You Yahoo!?
> Yahoo! Sports - sign up for Fantasy Baseball
> http://sports.yahoo.com
>
> —
> You are currently subscribed to windbg as:
> xxxxx@seagate.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
>
>
> —
> You are currently subscribed to windbg as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
%%email.unsub%%


Do You Yahoo!?
Try FREE Yahoo! Mail - the world’s greatest free email!
http://mail.yahoo.com/

Hi Philip,

I think this problem is solved.

Apparently after setting the bp, the source window
indeed came up(without using the call stack),
but for some reason it was hidden behind the
command window, thus, I never got the chance to see
it.
I also thought that the source should appear in the
command window(which currently shows the asm listing)
, should it ?!

Thanks for all the help.

-Mike.

— Mike Malgin wrote:
> Hi,
>
> Yes, I’m able to do a single-step, setting bp is
> also
> possible(I need to go back to the command window…
> on break it shows asm listing),
> the source seems to be correct and I’m also on the
> right statment, but cannot do step-in etc.
> The PDB file is about 400K larger then the sys file.
>
> Despite the above, is this the way it should work?
> I mean debugging through the local call stack?
>
> Thanks!
> -Mike.
>
>
>
> — xxxxx@seagate.com wrote:
> >
> > I don’t know if you mentioned that you could open
> a
> > source file from the
> > stack window before. Is the source file the
> correct
> > one? Does it open to
> > the right statement? If you do that, can you
> > single-step through your
> > code, set breakpoints, etc…?
> >
> > If none of the above is correct, it’s possible
> that
> > the PDB is corrupt
> > somehow. I don’t remember what combination of
> > SOURCES macros I used, but I
> > do remember that I once caused build to produce
> PDBs
> > that were very small,
> > without any useful information in them. The PDB
> > should be some, maybe a
> > lot, bigger than your driver binary, and should
> have
> > the fully qualified
> > filenames of your source files in it if you look
> at
> > it in Notepad.
> >
> > That might give you some ideas where to look…
> >
> > Phil
> >
> >
> >
> >
> > Mike Malgin @lists.osr.com on
> > 03/04/2002 02:36:52 PM
> >
> > Please respond to “Kernel Debugging Interest List”
> >
> >
> > Sent by: xxxxx@lists.osr.com
> >
> >
> > To: “Kernel Debugging Interest List”
> >
> > cc:
> >
> > Subject: [windbg] RE: Symbol Errors
> >
> >
> > Hi Philip,
> >
> > I’m using Windows 2000 DDK, the target is windows
> > 2K Pro.
> >
> > The weirdest thing is that when I look in the
> call
> > stack and click on my function a source window
> > comes
> > up, the other thing is that when I do ‘lml’ to
> > verify the symbols I can actually see the name of
> > the
> >
> > driver and the path of the PDB file, which means
> > the symbols are ok ?! (i think).
> >
> > On the other hand as you said I get “unknown sig
> > opened” every time when loading MY driver PDB
> > (even when doing according to your description)
> >
> > Thanks,
> > -Mike.
> >
> >
> >
> > — xxxxx@seagate.com wrote:
> > >
> > > What DDK are you using?
> > >
> > > The unknown PDB is a big part of your problem,
> but
> > I
> > > can’t think of any
> > > reason other than you are using the wrong
> compiler
> > > or linker in your build
> > > environment.
> > >
> > > Anyone else have any suggestions why the 'Bag
> > would
> > > complain about an
> > > “unknown PDB”, as opposed to “mismatched
> > > timestamps”? Or is that the
> > > current error message for mismatched symbols?
> > >
> > > Phil
> > >
> > >
> > >
> > >
> > > Mike Malgin @lists.osr.com
> on
> > > 03/04/2002 01:58:07 PM
> > >
> > > Please respond to “Kernel Debugging Interest
> List”
> > >
> > >
> > > Sent by: xxxxx@lists.osr.com
> > >
> > >
> > > To: “Kernel Debugging Interest List”
> > >
> > > cc:
> > >
> > > Subject: [windbg] RE: Symbol Errors
> > >
> > >
> > > Hi,
> > >
> > > Thanks the help.
> > > Unfortunately, nothing seems to work,
> > > so I guess I’m going to let it go for now.
> > >
> > > Thanks,
> > > -Mike.
> > >
> > >
> > >
> > >
> > > —
> > > You are currently subscribed to windbg as:
> > > xxxxx@yahoo.com
> > > To unsubscribe send a blank email to
> > %%email.unsub%%
> >
> >
> >
> > Do You Yahoo!?
> > Yahoo! Sports - sign up for Fantasy Baseball
> > http://sports.yahoo.com
> >
> > —
> > You are currently subscribed to windbg as:
> > xxxxx@seagate.com
> > To unsubscribe send a blank email to
> %%email.unsub%%
> >
> >
> >
> >
> > —
> > You are currently subscribed to windbg as:
> > xxxxx@yahoo.com
> > To unsubscribe send a blank email to
> %%email.unsub%%
>
>
>

> Do You Yahoo!?
> Try FREE Yahoo! Mail - the world’s greatest free
> email!
> http://mail.yahoo.com/
>
> —
> You are currently subscribed to windbg as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
%%email.unsub%%

__________________________________________________
Do You Yahoo!?
Try FREE Yahoo! Mail - the world’s greatest free email!
http://mail.yahoo.com/

A little off topic, but,
Philip Barila wrote:

As I reread all the quoted stuff
(which I have snipped for the benefit of the >digest readers),

THANK YOU!
I’ve spent so much time wading through 3-4 level quoted replies while
reading the digest, sometimes it’s hard to even see what the new post is.
I wish others were as considerate as you.

Now back to your regularly scheduled mailing list.

Carl Appellof
VERITAS Software Global Corporation

Mike,

It looks like everything is working right. You should see ASM in the
command window, but not the source. When you have the source window open,
single stepping should single step source lines, rather than single
instructions. Stepping in should work also. When the ASM window is the
focus, then it should single step instructions, and step in should only
work when the current instruction is a call.

Phil

Mike Malgin @lists.osr.com on 03/05/2002 04:18:18 AM

Please respond to “Kernel Debugging Interest List”

Sent by: xxxxx@lists.osr.com

To: “Kernel Debugging Interest List”
cc:

Subject: [windbg] RE: Symbol Errors

Hi Philip,

I think this problem is solved.

Apparently after setting the bp, the source window
indeed came up(without using the call stack),
but for some reason it was hidden behind the
command window, thus, I never got the chance to see
it.
I also thought that the source should appear in the
command window(which currently shows the asm listing)
, should it ?!

Thanks for all the help.

-Mike.

Ok. No more problems, I relieved :wink:
Philip and all the rest, Thanks again !!
xxxxx@seagate.com wrote:

Mike,

It looks like everything is working right. You
should see ASM in the
command window, but not the source. When you have
the source window open,
single stepping should single step source lines,
rather than single
instructions. Stepping in should work also. When
the ASM window is the
focus, then it should single step instructions, and
step in should only
work when the current instruction is a call.

Phil

Mike Malgin @lists.osr.com on
> 03/05/2002 04:18:18 AM
>
> Please respond to “Kernel Debugging Interest List”
>
>
> Sent by: xxxxx@lists.osr.com
>
>
> To: “Kernel Debugging Interest List”
>
> cc:
>
> Subject: [windbg] RE: Symbol Errors
>
>
> Hi Philip,
>
> I think this problem is solved.
>
> Apparently after setting the bp, the source window
> indeed came up(without using the call stack),
> but for some reason it was hidden behind the
> command window, thus, I never got the chance to see
> it.
> I also thought that the source should appear in the
> command window(which currently shows the asm
> listing)
> , should it ?!
>
> Thanks for all the help.
>
> -Mike.
>
>
>
> —
> You are currently subscribed to windbg as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
%%email.unsub%%

__________________________________________________
Do You Yahoo!?
Try FREE Yahoo! Mail - the world’s greatest free email!
http://mail.yahoo.com/