Good Afternoon, i apologise if this is a simple question, but i am currently
debugging an issue with a KMDF driver on a computer without internet access, i
have downloaded and installed several DDK’s and the correct OS symbols but
cannot find the wdf01000.pdb file anywhere, please could you tell me the best
way to get this without access to the symbol server?
Kind Regards
Mark
Sorry, but the internet symbol server IS the best way. That does not mean you have to always be connected to the internet to debug, but you do need frequent enough connection to keep your local symbol store updated. Also, maybe you simply misspelled it, but you need to be working with a WDK, and not a DDK. Most of us will assume you are several revs behind when we see DDK. Finally, of course a good question is “Why?”.
Gary G. Little
----- Original Message -----
From: “Mark Diggles”
To: “Windows System Software Devs Interest List”
Sent: Wednesday, March 30, 2011 7:08:24 AM
Subject: [ntdev] wdf01000.pdb
Good Afternoon, i apologise if this is a simple question, but i am currently debugging an issue with a KMDF driver on a computer without internet access, i have downloaded and installed several DDK’s and the correct OS symbols but cannot find the wdf01000.pdb file anywhere, please could you tell me the best way to get this without access to the symbol server?
Kind Regards
Mark
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Go to a location where you have internet access to the symbol server,
use windbg to fetch the appropriate symbols, and copy the downloaded
pdb file to wherever it is you need to debug without access to the
internet.
Mark Roddy
On Wed, Mar 30, 2011 at 8:08 AM, Mark Diggles wrote:
> Good Afternoon, i apologise if this is a simple question, but i am currently
> debugging an issue with a KMDF driver on a computer without internet access,
> i have downloaded and installed several DDK’s and the correct OS symbols but
> cannot find the wdf01000.pdb file anywhere, please could you tell me the
> best way to get this without access to the symbol server?
>
> Kind Regards
>
> Mark
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
I work for a secure company and my desktop cannot have internet access for legal
reasons,
I am currently using the WDK (6001.18002) as i need compatibility from windows
2000 to Windows 7, i am currently experiencing a win2000 only bug whereby
wdf01000.sys seems to be using address space assigned to my driver and
overwriting memoyr (leading to an irql_not_less_or_equal error) which i am
having trouble solving, this is my first foray into the world of driver
development.
Kind Regards
Mark
From: Gary G. Little
To: Windows System Software Devs Interest List
Sent: Wed, March 30, 2011 1:52:12 PM
Subject: Re: [ntdev] wdf01000.pdb
Sorry, but the internet symbol server IS the best way. That does not mean you
have to always be connected to the internet to debug, but you do need frequent
enough connection to keep your local symbol store updated. Also, maybe you
simply misspelled it, but you need to be working with a WDK, and not a DDK. Most
of us will assume you are several revs behind when we see DDK. Finally, of
course a good question is “Why?”.
Gary G. Little
----- Original Message -----
From: “Mark Diggles”
To: “Windows System Software Devs Interest List”
Sent: Wednesday, March 30, 2011 7:08:24 AM
Subject: [ntdev] wdf01000.pdb
Good Afternoon, i apologise if this is a simple question, but i am currently
debugging an issue with a KMDF driver on a computer without internet access, i
have downloaded and installed several DDK’s and the correct OS symbols but
cannot find the wdf01000.pdb file anywhere, please could you tell me the best
way to get this without access to the symbol server?
Kind Regards
Mark
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
If you use dual systems in a target/host connection, find an old dump file of your target OS, and have WinDbg open it while connected to the internet with the symbol server properly set up, and while of course NOT connected to your cloaked target. When your ready to debug the target, shutdown the internet and plug in your cloaked system.
You do know that you won’t find a WDF01000.pdb file for anything earlier than XP SP2, maybe SP3?
Is this really a “legal” issue, meaning to me your work environment is being controlled by a bunch of pointy haired suits that wouldn’t know C from pig-latin?
Gary G. Little
----- Original Message -----
From: “Mark Roddy”
To: “Windows System Software Devs Interest List”
Sent: Wednesday, March 30, 2011 7:56:59 AM
Subject: Re: [ntdev] wdf01000.pdb
Go to a location where you have internet access to the symbol server,
use windbg to fetch the appropriate symbols, and copy the downloaded
pdb file to wherever it is you need to debug without access to the
internet.
Mark Roddy
On Wed, Mar 30, 2011 at 8:08 AM, Mark Diggles wrote:
> Good Afternoon, i apologise if this is a simple question, but i am currently
> debugging an issue with a KMDF driver on a computer without internet access,
> i have downloaded and installed several DDK’s and the correct OS symbols but
> cannot find the wdf01000.pdb file anywhere, please could you tell me the
> best way to get this without access to the symbol server?
>
> Kind Regards
>
> Mark
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
That is unfortunately exactly the case.
I did not know that I could not find one for earlier, but surely their
is one for the co-installer that I am using (01007) ?
I am then unsure how to proceed in this case, I have got to the end of
my knowledge and wanted to post a crash dump but don’t want to do that
without using the correct symbols.
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: 30 March 2011 14:19
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] wdf01000.pdb
If you use dual systems in a target/host connection, find an old dump
file of your target OS, and have WinDbg open it while connected to the
internet with the symbol server properly set up, and while of course NOT
connected to your cloaked target. When your ready to debug the target,
shutdown the internet and plug in your cloaked system.
You do know that you won’t find a WDF01000.pdb file for anything earlier
than XP SP2, maybe SP3?
Is this really a “legal” issue, meaning to me your work environment is
being controlled by a bunch of pointy haired suits that wouldn’t know C
from pig-latin?
Gary G. Little
----- Original Message -----
From: “Mark Roddy”
To: “Windows System Software Devs Interest List”
Sent: Wednesday, March 30, 2011 7:56:59 AM
Subject: Re: [ntdev] wdf01000.pdb
Go to a location where you have internet access to the symbol server,
use windbg to fetch the appropriate symbols, and copy the downloaded
pdb file to wherever it is you need to debug without access to the
internet.
Mark Roddy
On Wed, Mar 30, 2011 at 8:08 AM, Mark Diggles
wrote:
> Good Afternoon, i apologise if this is a simple question, but i am
currently
> debugging an issue with a KMDF driver on a computer without internet
access,
> i have downloaded and installed several DDK’s and the correct OS
symbols but
> cannot find the wdf01000.pdb file anywhere, please could you tell me
the
> best way to get this without access to the symbol server?
>
> Kind Regards
>
> Mark
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Please consider the environment before printing this email.
This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately.
Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory. The contents of this email may relate to dealings with other companies within the Detica Limited group of companies.
Detica Limited is registered in England under No: 1337451.
Registered offices: Surrey Research Park, Guildford, Surrey, GU2 7YP, England.
Well, one thing you can do is force a crash on your target system and OS, copy the dump file to your host and open the dump file in WinDbg using Ctrl-K with the symbol server setup as described earlier. That should give you a decent set of symbols. Then sanitize your environment and go do some debugging with the live target.
Gary G. Little
----- Original Message -----
From: “Mark Diggles”
To: “Windows System Software Devs Interest List”
Sent: Wednesday, March 30, 2011 8:28:09 AM
Subject: RE: [ntdev] wdf01000.pdb
That is unfortunately exactly the case.
I did not know that I could not find one for earlier, but surely their is one for the co-installer that I am using (01007) ?
I am then unsure how to proceed in this case, I have got to the end of my knowledge and wanted to post a crash dump but don’t want to do that without using the correct symbols.
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: 30 March 2011 14:19
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] wdf01000.pdb
If you use dual systems in a target/host connection, find an old dump file of your target OS, and have WinDbg open it while connected to the internet with the symbol server properly set up, and while of course NOT connected to your cloaked target. When your ready to debug the target, shutdown the internet and plug in your cloaked system.
You do know that you won’t find a WDF01000.pdb file for anything earlier than XP SP2, maybe SP3?
Is this really a “legal” issue, meaning to me your work environment is being controlled by a bunch of pointy haired suits that wouldn’t know C from pig-latin?
Gary G. Little
----- Original Message -----
From: “Mark Roddy”
To: “Windows System Software Devs Interest List”
Sent: Wednesday, March 30, 2011 7:56:59 AM
Subject: Re: [ntdev] wdf01000.pdb
Go to a location where you have internet access to the symbol server,
use windbg to fetch the appropriate symbols, and copy the downloaded
pdb file to wherever it is you need to debug without access to the
internet.
Mark Roddy
On Wed, Mar 30, 2011 at 8:08 AM, Mark Diggles wrote:
> Good Afternoon, i apologise if this is a simple question, but i am currently
> debugging an issue with a KMDF driver on a computer without internet access,
> i have downloaded and installed several DDK’s and the correct OS symbols but
> cannot find the wdf01000.pdb file anywhere, please could you tell me the
> best way to get this without access to the symbol server?
>
> Kind Regards
>
> Mark
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer Please consider the environment before printing this email.
This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately.
Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory. The contents of this email may relate to dealings with other companies within the Detica Limited group of companies.
Detica Limited is registered in England under No: 1337451.
Registered offices: Surrey Research Park, Guildford, Surrey, GU2 7YP, England.
Not having internet access on your development machine is fairly common
practice these days, I come across it with LOTS of the students that I
teach. It does cause issues when it comes to symbols though. In a lot of
cases it’s basically the ONLY way to get symbols for images, so it’s
definitely a speed bump when you’re just trying to get your work done.
Everything suggested here will work. In addition, WinDBG will let you open
individual executable files and that can be a fast way to grab symbols for
something. Just copy the SYS file to a system connected to the internet with
WinDBG installed and open the SYS file the same way you would open a crash
dump. You can then use the “lmv” command to see the path to the PDB that was
downloaded.
If this is a constant issue for you and you would like to automate this, see
the dumpstk (“stack”, not “stick” :)) sample in the debugger SDK. This shows
how to open something as a crash dump in a standalone application, so you
wouldn’t even need to use WinDBG.
For your sake and the sake of your co-workers, I also suggest setting up an
internal symbol server that you copy all of these things to so that you
won’t have to deal with it in the future. As you all contribute random PDBs
to it you’ll hopefully eventually run into this less and less. See the
documentation for symstore in the WinDBG help for more details.
Good luck!
-scott
–
Scott Noone
Consulting Associate and Chief System Problem Analyst
OSR Open Systems Resources, Inc.
http://www.osronline.com
Mark Diggles wrote:
Good Afternoon, i apologise if this is a simple question, but i am
currently debugging an issue with a KMDF driver on a computer without
internet access, i have downloaded and installed several DDK’s and the
correct OS symbols but cannot find the wdf01000.pdb file anywhere,
please could you tell me the best way to get this without access to
the symbol server?
One thing you need to bear in mind here. Each version of KMDF (1.0,
1.1, 1.5, 1.7, 1.9) has its own version of wdf01000.sys and
wdf01000.pdb. They all have the same file name. If you decide to load
this from the symbol server and copy the files, be careful that you copy
the right ones. To be safe, you probably want to copy ALL of them.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
For your sake and the sake of your co-workers, I also suggest setting up an
internal symbol server that you copy all of these things to so that you
won’t have to deal with it in the future. As you all contribute random PDBs
to it you’ll hopefully eventually run into this less and less. See the
documentation for symstore in the WinDBG help for more details.
+1
I more often than not may not be connected to the internet for work I do, and this is by far the best way to go, in my opinion.
You can ‘prime’ this operation by download symbol packs, though in practice I usually run a program I wrote that profiles the hard drive of a target, looking for the matching pdb information in the PE headers and uses it to generate a text file that contains the necessary urls to pull everything from the msft symbol server. I then use that text file on an internet connected machine to download everything, and then push those files to either a symbol directory (formatted as symbol server would), or an internal symbol server.
Kind of a pain, but not having matching symbols is a huge problem, and having to download them as needed can be a pain.
Good luck,
mm
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Wednesday, March 30, 2011 11:45 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] wdf01000.pdb
Not having internet access on your development machine is fairly common
practice these days, I come across it with LOTS of the students that I
teach. It does cause issues when it comes to symbols though. In a lot of
cases it’s basically the ONLY way to get symbols for images, so it’s
definitely a speed bump when you’re just trying to get your work done.
Everything suggested here will work. In addition, WinDBG will let you open
individual executable files and that can be a fast way to grab symbols for
something. Just copy the SYS file to a system connected to the internet with
WinDBG installed and open the SYS file the same way you would open a crash
dump. You can then use the “lmv” command to see the path to the PDB that was
downloaded.
If this is a constant issue for you and you would like to automate this, see
the dumpstk (“stack”, not “stick” :)) sample in the debugger SDK. This shows
how to open something as a crash dump in a standalone application, so you
wouldn’t even need to use WinDBG.
For your sake and the sake of your co-workers, I also suggest setting up an
internal symbol server that you copy all of these things to so that you
won’t have to deal with it in the future. As you all contribute random PDBs
to it you’ll hopefully eventually run into this less and less. See the
documentation for symstore in the WinDBG help for more details.
Good luck!
-scott
–
Scott Noone
Consulting Associate and Chief System Problem Analyst
OSR Open Systems Resources, Inc.
http://www.osronline.com
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
I’ve never understood why a requirement to be isolated is seen as silly, et. c. I mean, it’s a huge pita, to be sure, but it’s actually not that uncommon. Sometimes it’s due to working in secure facilities, but more commonly, in my experience, it’s due to concern over IP going out the door whether intentionally, unintentionally or forcibly. In any event, good, bad or otherwise, those of us who have to deal with it are stuck with it, and wanting access to the msft symbol server is never going to fly as a reason to circumvent the system.
mm
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Wednesday, March 30, 2011 9:19 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] wdf01000.pdb
If you use dual systems in a target/host connection, find an old dump file of your target OS, and have WinDbg open it while connected to the internet with the symbol server properly set up, and while of course NOT connected to your cloaked target. When your ready to debug the target, shutdown the internet and plug in your cloaked system.
You do know that you won’t find a WDF01000.pdb file for anything earlier than XP SP2, maybe SP3?
Is this really a “legal” issue, meaning to me your work environment is being controlled by a bunch of pointy haired suits that wouldn’t know C from pig-latin?
Gary G. Little
----- Original Message -----
From: “Mark Roddy”
To: “Windows System Software Devs Interest List”
Sent: Wednesday, March 30, 2011 7:56:59 AM
Subject: Re: [ntdev] wdf01000.pdb
Go to a location where you have internet access to the symbol server,
use windbg to fetch the appropriate symbols, and copy the downloaded
pdb file to wherever it is you need to debug without access to the
internet.
Mark Roddy
On Wed, Mar 30, 2011 at 8:08 AM, Mark Diggles wrote:
> Good Afternoon, i apologise if this is a simple question, but i am currently
> debugging an issue with a KMDF driver on a computer without internet access,
> i have downloaded and installed several DDK’s and the correct OS symbols but
> cannot find the wdf01000.pdb file anywhere, please could you tell me the
> best way to get this without access to the symbol server?
>
> Kind Regards
>
> Mark
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
What does surprise me is that you are allowed to post a crash dump but NOT
connect to symbol server.
mm
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mark Diggles
Sent: Wednesday, March 30, 2011 9:28 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] wdf01000.pdb
That is unfortunately exactly the case.
I did not know that I could not find one for earlier, but surely their is
one for the co-installer that I am using (01007) ?
I am then unsure how to proceed in this case, I have got to the end of my
knowledge and wanted to post a crash dump but don’t want to do that without
using the correct symbols.
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: 30 March 2011 14:19
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] wdf01000.pdb
If you use dual systems in a target/host connection, find an old dump file
of your target OS, and have WinDbg open it while connected to the internet
with the symbol server properly set up, and while of course NOT connected to
your cloaked target. When your ready to debug the target, shutdown the
internet and plug in your cloaked system.
You do know that you won’t find a WDF01000.pdb file for anything earlier
than XP SP2, maybe SP3?
Is this really a “legal” issue, meaning to me your work environment is being
controlled by a bunch of pointy haired suits that wouldn’t know C from
pig-latin?
Gary G. Little
----- Original Message -----
From: “Mark Roddy”
To: “Windows System Software Devs Interest List”
Sent: Wednesday, March 30, 2011 7:56:59 AM
Subject: Re: [ntdev] wdf01000.pdb
Go to a location where you have internet access to the symbol server,
use windbg to fetch the appropriate symbols, and copy the downloaded
pdb file to wherever it is you need to debug without access to the
internet.
Mark Roddy
On Wed, Mar 30, 2011 at 8:08 AM, Mark Diggles wrote:
> Good Afternoon, i apologise if this is a simple question, but i am
currently
> debugging an issue with a KMDF driver on a computer without internet
access,
> i have downloaded and installed several DDK’s and the correct OS symbols
but
> cannot find the wdf01000.pdb file anywhere, please could you tell me the
> best way to get this without access to the symbol server?
>
> Kind Regards
>
> Mark
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Please consider the environment before printing this email.
This message should be regarded as confidential. If you have received this
email in error please notify the sender and destroy it immediately.
Statements of intent shall only become binding when confirmed in hard copy
by an authorised signatory. The contents of this email may relate to
dealings with other companies within the Detica Limited group of companies.
Detica Limited is registered in England under No: 1337451.
Registered offices: Surrey Research Park, Guildford, Surrey, GU2 7YP,
England.
On 03/30/2011 11:19 PM, Martin O’Brien wrote:
[More commonly, not allowing Internet access from development
machines is] due to concern over IP going out the door whether
intentionally, unintentionally or forcibly.
+1
Reasons to deny Internet access in IP-sensitive environments are e.g.:
applications and OS components “calling home” without being very
transparent about what data are transferred and for what purpose
(e.g. OLPC tried to solve this using certified app-profiles), and
transparent Internet proxy server company infrastructure that allows
any malicious program pseudo-direct access to the Internet.
In any event, good, bad or otherwise, those of us who have to deal
with it are stuck with it, and wanting access to the msft symbol
server is never going to fly as a reason to circumvent the system.
A local symbol server should not be a problem, of course, especially
if it’s possible to preload it with symbols from e.g. the MSDN library.
> What does surprise me is that you are allowed to post a crash dump but
NOT connect to symbol server.
No surprise here: it’s incoming versus outgoing connections.
There are ITSOs who have no problem with completely unmonitored email,
but will deny requests for any inbound data connection, or connecting to
any ‘uncommon’ external port.
This is the issue, it is not even an IP issue but more a legal
restriction (and no not just suits but the nature of our work
(forensics)). I would love to pre-load a local symbol server if I were
able to get the required symbols from somewhere (wdf01000.pdb) without
crashing a target machine with internet connectivity which it looks like
I will have to resort to.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Hagen Patzke
Sent: 31 March 2011 08:37
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] wdf01000.pdb
On 03/30/2011 11:19 PM, Martin O’Brien wrote:
[More commonly, not allowing Internet access from development machines
is] due to concern over IP going out the door whether intentionally,
unintentionally or forcibly.
+1
Reasons to deny Internet access in IP-sensitive environments are e.g.:
applications and OS components “calling home” without being very
transparent about what data are transferred and for what purpose (e.g.
OLPC tried to solve this using certified app-profiles), and
transparent Internet proxy server company infrastructure that allows
any malicious program pseudo-direct access to the Internet.
In any event, good, bad or otherwise, those of us who have to deal
with it are stuck with it, and wanting access to the msft symbol
server is never going to fly as a reason to circumvent the system.
A local symbol server should not be a problem, of course, especially
if it’s possible to preload it with symbols from e.g. the MSDN library.
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Please consider the environment before printing this email.
This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately.
Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory. The contents of this email may relate to dealings with other companies within the Detica Limited group of companies.
Detica Limited is registered in England under No: 1337451.
Registered offices: Surrey Research Park, Guildford, Surrey, GU2 7YP, England.
It’s really the only practical way. Given service packs, Windows Update, and blah blah blah blah… sometimes you’re lucky if even the symbols on the symbol server are right.
In terms of JUST the WDF symbols, perhaps our friends at Microsoft will take this as a request to include the WDF PDB in future releases of the WDK… or perhaps post them online for download. There are LOTS of cases where one can be “stuck” debugging in a situation where there’s no access to the symbol server… KMDF is now used widely enough that having those symbols is imperative, because having to trace an error in a KMDF driver with NO Framework symbols can be pretty grim.
If somebody (such as Doron) doesn’t notice this and respond in the affirmative in the next day or so, I’ll file a bug on this (assuming I can figure out the All New And Improved Bug System, this will be my test case).
Peter
OSR
Policy is that we don’t post symbols individually in kits anymore. The symbol server fixes that problem for the general population. You can set up a private server if you can’t hit the web, I think there is a way to slurp all the symbols off of the official server so you can populate yours.
You can file a big if you want, but given what I just described it will be closed as “won’t fix.”
d
dent from a phine with no keynoard
-----Original Message-----
From: xxxxx@osr.com
Sent: Thursday, March 31, 2011 6:46 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] wdf01000.pdb
It’s really the only practical way. Given service packs, Windows Update, and blah blah blah blah… sometimes you’re lucky if even the symbols on the symbol server are right.
In terms of JUST the WDF symbols, perhaps our friends at Microsoft will take this as a request to include the WDF PDB in future releases of the WDK… or perhaps post them online for download. There are LOTS of cases where one can be “stuck” debugging in a situation where there’s no access to the symbol server… KMDF is now used widely enough that having those symbols is imperative, because having to trace an error in a KMDF driver with NO Framework symbols can be pretty grim.
If somebody (such as Doron) doesn’t notice this and respond in the affirmative in the next day or so, I’ll file a bug on this (assuming I can figure out the All New And Improved Bug System, this will be my test case).
Peter
OSR
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Hmmmm… The symbol server existed even when the symbols were included in the kits. The symbols for NTOS and HAL were included specifically to counteract the problem of not having internet access… or not having high-speed internet access.
Sigh…
Hmmm… Not aware of that. Can you, perhaps, elaborate? Cuz that would certainly eliminate the need to put the symbols in the kit. Sort of “do it yourself” slurping.
Something other than “Hook up WinDbg to a debugging system identical to the desired target and get it to download symbols to the symbol store” would be helpful.
Peter
OSR
Hi!
Setting up a local Symbol Server is very straitforward, and it is also documented very well.
From “Debugging Tools for Windows\symproxy\symhttp.doc”:
…
* Your corporate computing environment includes a firewall that prevents access to the internet from computers that are debugging and you need to get symbols from an internet web site such as http://msdl.microsoft.com/download/symbols.
…
When you apply this configuration, you (and potentially others without direct www access) connect though an internal Symbol-Server (IIS), which may connect to msdl.microsoft.com automatically to get to MS Symbols if needed.
You can even add you own Symbols there with ‘symstore.exe’.
GP
“Mark Diggles” schrieb im Newsbeitrag news:…
This is the issue, it is not even an IP issue but more a legal
restriction (and no not just suits but the nature of our work
(forensics)). I would love to pre-load a local symbol server if I were
able to get the required symbols from somewhere (wdf01000.pdb) without
crashing a target machine with internet connectivity which it looks like
I will have to resort to.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Hagen Patzke
Sent: 31 March 2011 08:37
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] wdf01000.pdb
On 03/30/2011 11:19 PM, Martin O’Brien wrote:
> [More commonly, not allowing Internet access from development machines
> is] due to concern over IP going out the door whether intentionally,
> unintentionally or forcibly.
+1
Reasons to deny Internet access in IP-sensitive environments are e.g.:
- applications and OS components “calling home” without being very
transparent about what data are transferred and for what purpose (e.g.
OLPC tried to solve this using certified app-profiles), and
- transparent Internet proxy server company infrastructure that allows
any malicious program pseudo-direct access to the Internet.
> In any event, good, bad or otherwise, those of us who have to deal
> with it are stuck with it, and wanting access to the msft symbol
> server is never going to fly as a reason to circumvent the system.
A local symbol server should not be a problem, of course, especially
if it’s possible to preload it with symbols from e.g. the MSDN library.
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Please consider the environment before printing this email.
This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately.
Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory. The contents of this email may relate to dealings with other companies within the Detica Limited group of companies.
Detica Limited is registered in England under No: 1337451.
Registered offices: Surrey Research Park, Guildford, Surrey, GU2 7YP, England.
----------
You can do this with symchk, provided of course that you can run symchk on
the machine in question and that the machine in question has appropriate
internet access.
mm
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@osr.com
Sent: Thursday, March 31, 2011 11:29 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] wdf01000.pdb
Hmmmm… The symbol server existed even when the symbols were included in
the kits. The symbols for NTOS and HAL were included specifically to
counteract the problem of not having internet access… or not having
high-speed internet access.
Sigh…
Hmmm… Not aware of that. Can you, perhaps, elaborate? Cuz that would
certainly eliminate the need to put the symbols in the kit. Sort of “do it
yourself” slurping.
Something other than “Hook up WinDbg to a debugging system identical to the
desired target and get it to download symbols to the symbol store” would be
helpful.
Peter
OSR
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer