Any chance we could lose the following annoying message? I’m well aware I
don’t have private OS symbols. I get 5 of these in the middle of the output
of !analyze with windbg 6.6.0003.5.
Thanks,
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
This has been fixed for a while now. Try deleting the mssmbios.pdb directory
from your local symbol store and reloading.
-scott
–
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Dan Kyler” wrote in message news:xxxxx@windbg…
> Any chance we could lose the following annoying message? I’m well aware I
> don’t have private OS symbols. I get 5 of these in the middle of the
> output of !analyze with windbg 6.6.0003.5.
>
> Thanks,
> - Dan.
>
>
>
>
> Your debugger is not using the correct symbols
>
> In order for this command to work properly, your symbol path
> must point to .pdb files that have full type information.
>
> Certain .pdb files (such as the public OS symbols) do not
> contain the required information. Contact the group that
> provided you with these symbols if you need this command to
> work.
>
> Type referenced: mssmbios!_SMBIOS_DATA_OBJECT
>
>
>
>
>
That appears to have worked. Thanks.
So this was a problem with the symbol file on the public symbol server?
Thanks,
“Scott Noone” wrote in message
news:…
> This has been fixed for a while now. Try deleting the mssmbios.pdb
> directory
> from your local symbol store and reloading.
>
> -scott
>
> –
> Scott Noone
> Software Engineer
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
> “Dan Kyler” wrote in message news:xxxxx@windbg…
> > Any chance we could lose the following annoying message? I’m well
> > aware I
> > don’t have private OS symbols. I get 5 of these in the middle of the
> > output of !analyze with windbg 6.6.0003.5.
> >
> > Thanks,
> > - Dan.
> >
> > *****
> >
> >
> > Your debugger is not using the correct symbols
> >
> > In order for this command to work properly, your symbol path
> > must point to .pdb files that have full type information.
> >
> > Certain .pdb files (such as the public OS symbols) do not
> > contain the required information. Contact the group that
> > provided you with these symbols if you need this command to
> > work.
> >
> > Type referenced: mssmbios!_SMBIOS_DATA_OBJECT
> >
> >
> > *****
> >
> >
> >
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@privtek.com To
> unsubscribe send a blank email to xxxxx@lists.osr.
Yeah, the previous version of mssmbios.pdb had all the type information
stripped out.
-scott
–
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Dan Kyler” wrote in message news:xxxxx@windbg…
> That appears to have worked. Thanks.
>
> So this was a problem with the symbol file on the public symbol server?
>
> Thanks,
>
> - Dan.
>
>
>
> “Scott Noone” wrote in message
> news:…
>
>> This has been fixed for a while now. Try deleting the mssmbios.pdb
>
>> directory
>
>> from your local symbol store and reloading.
>
>>
>
>> -scott
>
>>
>
>> –
>
>> Scott Noone
>
>> Software Engineer
>
>> OSR Open Systems Resources, Inc.
>
>> http://www.osronline.com
>
>>
>
>> “Dan Kyler” wrote in message news:xxxxx@windbg…
>
>> > Any chance we could lose the following annoying message? I’m well
>
>> > aware I
>
>> > don’t have private OS symbols. I get 5 of these in the middle of the
>
>> > output of !analyze with windbg 6.6.0003.5.
>
>> >
>
>> > Thanks,
>
>> > - Dan.
>
>> >
>
>> > *****
>
>> >
>
>> >
>
>> > Your debugger is not using the correct symbols
>
>> >
>
>> > In order for this command to work properly, your symbol path
>
>> > must point to .pdb files that have full type information.
>
>> >
>
>> > Certain .pdb files (such as the public OS symbols) do not
>
>> > contain the required information. Contact the group that
>
>> > provided you with these symbols if you need this command to
>
>> > work.
>
>> >
>
>> > Type referenced: mssmbios!_SMBIOS_DATA_OBJECT
>
>> >
>
>> >
>
>> > *****
>
>> >
>
>> >
>
>> >
>
>>
>
>>
>
>>
>
>> —
>
>> You are currently subscribed to windbg as: xxxxx@privtek.com To
>
>> unsubscribe send a blank email to xxxxx@lists.osr.
>
>
>
Has anyone told the boys and girls that did the SMBIOS driver they have a
bug that fails in verifier, and that they forgot to turn off debug print
mesaages? This is critical since HCT test tends to fail because some test
cases require testing of the SMBIOS driver.
Hmm … or are the SMBIOS messages and faults I see contained in
mssmbios.sys?
Gary G. Little
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Dan Kyler
Sent: Thursday, March 16, 2006 12:08 PM
To: Kernel Debugging Interest List
Subject: RE:[windbg] Annoying symbol messages
That appears to have worked. Thanks.
So this was a problem with the symbol file on the public symbol server?
Thanks,
“Scott Noone” wrote in message
news:…
> This has been fixed for a while now. Try deleting the mssmbios.pdb
> directory
> from your local symbol store and reloading.
>
> -scott
>
> –
> Scott Noone
> Software Engineer
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
> “Dan Kyler” wrote in message news:xxxxx@windbg…
> > Any chance we could lose the following annoying message? I’m well
> > aware I
> > don’t have private OS symbols. I get 5 of these in the middle of the
> > output of !analyze with windbg 6.6.0003.5.
> >
> > Thanks,
> > - Dan.
> >
> >
*****
> >
> >
> > Your debugger is not using the correct symbols
> >
> > In order for this command to work properly, your symbol path
> > must point to .pdb files that have full type information.
> >
> > Certain .pdb files (such as the public OS symbols) do not
> > contain the required information. Contact the group that
> > provided you with these symbols if you need this command to
> > work.
> >
> > Type referenced: mssmbios!_SMBIOS_DATA_OBJECT
> >
> >
> > *****
> >
> >
> >
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@privtek.com To
> unsubscribe send a blank email to xxxxx@lists.osr.
—
You are currently subscribed to windbg as: xxxxx@seagate.com
To unsubscribe send a blank email to xxxxx@lists.osr.com