So I am still seeing this upon occasion. I have no watch expressions, no breakpoints; I do an unload of a specific DLL and WinDbg keeps a handle open to the .PDB still.
-Jeff
Pretty much; I know of at least one other person whom I trust that has seen this as well.
I haven’t seen it a whole lot, but it has been uncommon either. I haven’t bothered to try to
reproduce it, nor have any intention of doing so, as it seems like a forgone conclusion to me at
this point that what I will get back from msft if work this up is at best an e-mail saying they
couldn’t reproduce it.
mm
Jeff Curless wrote:
So I am still seeing this upon occasion. I have no watch expressions, no breakpoints; I do an unload of a specific DLL and WinDbg keeps a handle open to the .PDB still.
-Jeff
Please try the latest debugger. We found out and fixed a possible problem there. If you continue hit the PDB handle issue from the latest release, please let us know and we will try repro the fix them.
Thanks,
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Thursday, March 26, 2009 11:34 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Windbg still not releasing handle to .pdb
Pretty much; I know of at least one other person whom I trust that has seen this as well.
I haven’t seen it a whole lot, but it has been uncommon either. I haven’t bothered to try to
reproduce it, nor have any intention of doing so, as it seems like a forgone conclusion to me at
this point that what I will get back from msft if work this up is at best an e-mail saying they
couldn’t reproduce it.
mm
Jeff Curless wrote:
So I am still seeing this upon occasion. I have no watch expressions, no breakpoints; I do an unload of a specific DLL and WinDbg keeps a handle open to the .PDB still.
-Jeff
WINDBG 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 reported it last month, but I’m still hitting it frequently with the
latest available release…
For me, it seems to be most evident when debugging applications launched by
WinDBG (Ctrl+E). Over the last couple of days I resorted to having
ProcessExplorer’s “search handle” dialog up so I can close the 1-4
outstanding handles without having to quit WinDBG between builds.
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Jen-Lung Chiu” wrote in message
news:xxxxx@windbg…
Please try the latest debugger. We found out and fixed a possible problem
there. If you continue hit the PDB handle issue from the latest release,
please let us know and we will try repro the fix them.
Thanks,
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Thursday, March 26, 2009 11:34 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Windbg still not releasing handle to .pdb
Pretty much; I know of at least one other person whom I trust that has seen
this as well.
I haven’t seen it a whole lot, but it has been uncommon either. I haven’t
bothered to try to
reproduce it, nor have any intention of doing so, as it seems like a forgone
conclusion to me at
this point that what I will get back from msft if work this up is at best an
e-mail saying they
couldn’t reproduce it.
mm
Jeff Curless wrote:
> So I am still seeing this upon occasion. I have no watch expressions, no
> breakpoints; I do an unload of a specific DLL and WinDbg keeps a handle
> open to the .PDB still.
>
> -Jeff
>
—
WINDBG 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
+1 as far as having seen with 6.11.1.402, and also as far as reporting it, though to be fair, I
didn’t report it via the windbg alias, but I was told that the windbg folks already knew about it.
I don’t really know what happened, but I guess that it doesn’t really matter either, as at least the
ever dependable Snoone reported it.
As far as the conditions involved, I have no idea, other than to say that mine had to be different,
as Ctrl+E was totally unknown to me until just now.
mm
Scott Noone wrote:
I reported it last month, but I’m still hitting it frequently with the
latest available release…For me, it seems to be most evident when debugging applications launched by
WinDBG (Ctrl+E). Over the last couple of days I resorted to having
ProcessExplorer’s “search handle” dialog up so I can close the 1-4
outstanding handles without having to quit WinDBG between builds.-scott
> As far as the conditions involved, I have no idea, other than to say that
mine had to be different, as Ctrl+E was totally unknown to me until just
now.
You mean you don’t debug your apps with WinDBG? For shame…
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Martin O’Brien” wrote in message
news:xxxxx@windbg…
> +1 as far as having seen with 6.11.1.402, and also as far as reporting it,
> though to be fair, I didn’t report it via the windbg alias, but I was told
> that the windbg folks already knew about it. I don’t really know what
> happened, but I guess that it doesn’t really matter either, as at least
> the ever dependable Snoone reported it.
>
> As far as the conditions involved, I have no idea, other than to say that
> mine had to be different, as Ctrl+E was totally unknown to me until just
> now.
>
> mm
>
>
>
>
>
>
>
>
> Scott Noone wrote:
>> I reported it last month, but I’m still hitting it frequently with the
>> latest available release…
>>
>> For me, it seems to be most evident when debugging applications launched
>> by WinDBG (Ctrl+E). Over the last couple of days I resorted to having
>> ProcessExplorer’s “search handle” dialog up so I can close the 1-4
>> outstanding handles without having to quit WinDBG between builds.
>>
>> -scott
>>
>
Please verify your debugger version. Is it 6.11.1.402 or 6.11.1.404? There should be another debugger update (6.11.1.404) in early March that fixes one PDB handle issue we finally found out. The site http://www.microsoft.com/whdc/devtools/debugging/default.mspx does not update the version, but if you click the link and upgrade, it should be build 404.
If you still repro the problem from 6.11.1.404, please let us know and we will look into this.
Thanks,
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Thursday, March 26, 2009 12:51 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Windbg still not releasing handle to .pdb
As far as the conditions involved, I have no idea, other than to say that
mine had to be different, as Ctrl+E was totally unknown to me until just
now.
You mean you don’t debug your apps with WinDBG? For shame…
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Martin O’Brien” wrote in message
news:xxxxx@windbg…
> +1 as far as having seen with 6.11.1.402, and also as far as reporting it,
> though to be fair, I didn’t report it via the windbg alias, but I was told
> that the windbg folks already knew about it. I don’t really know what
> happened, but I guess that it doesn’t really matter either, as at least
> the ever dependable Snoone reported it.
>
> As far as the conditions involved, I have no idea, other than to say that
> mine had to be different, as Ctrl+E was totally unknown to me until just
> now.
>
> mm
>
>
>
>
>
>
>
>
> Scott Noone wrote:
>> I reported it last month, but I’m still hitting it frequently with the
>> latest available release…
>>
>> For me, it seems to be most evident when debugging applications launched
>> by WinDBG (Ctrl+E). Over the last couple of days I resorted to having
>> ProcessExplorer’s “search handle” dialog up so I can close the 1-4
>> outstanding handles without having to quit WinDBG between builds.
>>
>> -scott
>>
>
—
WINDBG 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
Spooky! OK, just downloaded dbg_x86_6.11.1.402.msi, which installed version
6.11.1.404.
Anything else different in this release or just the PDB fix?
Thanks,
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Jen-Lung Chiu” wrote in message
news:xxxxx@windbg…
Please verify your debugger version. Is it 6.11.1.402 or 6.11.1.404? There
should be another debugger update (6.11.1.404) in early March that fixes one
PDB handle issue we finally found out. The site
http://www.microsoft.com/whdc/devtools/debugging/default.mspx does not
update the version, but if you click the link and upgrade, it should be
build 404.
If you still repro the problem from 6.11.1.404, please let us know and we
will look into this.
Thanks,
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Thursday, March 26, 2009 12:51 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Windbg still not releasing handle to .pdb
> As far as the conditions involved, I have no idea, other than to say that
> mine had to be different, as Ctrl+E was totally unknown to me until just
> now.
You mean you don’t debug your apps with WinDBG? For shame…
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Martin O’Brien” wrote in message
news:xxxxx@windbg…
> +1 as far as having seen with 6.11.1.402, and also as far as reporting it,
> though to be fair, I didn’t report it via the windbg alias, but I was told
> that the windbg folks already knew about it. I don’t really know what
> happened, but I guess that it doesn’t really matter either, as at least
> the ever dependable Snoone reported it.
>
> As far as the conditions involved, I have no idea, other than to say that
> mine had to be different, as Ctrl+E was totally unknown to me until just
> now.
>
> mm
>
>
>
>
>
>
>
>
> Scott Noone wrote:
>> I reported it last month, but I’m still hitting it frequently with the
>> latest available release…
>>
>> For me, it seems to be most evident when debugging applications launched
>> by WinDBG (Ctrl+E). Over the last couple of days I resorted to having
>> ProcessExplorer’s “search handle” dialog up so I can close the 1-4
>> outstanding handles without having to quit WinDBG between builds.
>>
>> -scott
>>
>
—
WINDBG 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
Also the “!symfix” problem you reported 
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Thursday, March 26, 2009 01:05 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Re:Windbg still not releasing handle to .pdb
Spooky! OK, just downloaded dbg_x86_6.11.1.402.msi, which installed version
6.11.1.404.
Anything else different in this release or just the PDB fix?
Thanks,
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Jen-Lung Chiu” wrote in message
news:xxxxx@windbg…
Please verify your debugger version. Is it 6.11.1.402 or 6.11.1.404? There
should be another debugger update (6.11.1.404) in early March that fixes one
PDB handle issue we finally found out. The site
http://www.microsoft.com/whdc/devtools/debugging/default.mspx does not
update the version, but if you click the link and upgrade, it should be
build 404.
If you still repro the problem from 6.11.1.404, please let us know and we
will look into this.
Thanks,
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Thursday, March 26, 2009 12:51 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Windbg still not releasing handle to .pdb
> As far as the conditions involved, I have no idea, other than to say that
> mine had to be different, as Ctrl+E was totally unknown to me until just
> now.
You mean you don’t debug your apps with WinDBG? For shame…
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Martin O’Brien” wrote in message
news:xxxxx@windbg…
> +1 as far as having seen with 6.11.1.402, and also as far as reporting it,
> though to be fair, I didn’t report it via the windbg alias, but I was told
> that the windbg folks already knew about it. I don’t really know what
> happened, but I guess that it doesn’t really matter either, as at least
> the ever dependable Snoone reported it.
>
> As far as the conditions involved, I have no idea, other than to say that
> mine had to be different, as Ctrl+E was totally unknown to me until just
> now.
>
> mm
>
>
>
>
>
>
>
>
> Scott Noone wrote:
>> I reported it last month, but I’m still hitting it frequently with the
>> latest available release…
>>
>> For me, it seems to be most evident when debugging applications launched
>> by WinDBG (Ctrl+E). Over the last couple of days I resorted to having
>> ProcessExplorer’s “search handle” dialog up so I can close the 1-4
>> outstanding handles without having to quit WinDBG between builds.
>>
>> -scott
>>
>
—
WINDBG 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
—
WINDBG 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
Just thought I’d mention that after almost two weeks of beating on it, I
haven’t seen the PDB lock problem again. Looks like the demon has been
expelled!
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Jen-Lung Chiu” wrote in message
news:xxxxx@windbg…
Also the “!symfix” problem you reported
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Thursday, March 26, 2009 01:05 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Re:Windbg still not releasing handle to .pdb
Spooky! OK, just downloaded dbg_x86_6.11.1.402.msi, which installed version
6.11.1.404.
Anything else different in this release or just the PDB fix?
Thanks,
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Jen-Lung Chiu” wrote in message
news:xxxxx@windbg…
Please verify your debugger version. Is it 6.11.1.402 or 6.11.1.404? There
should be another debugger update (6.11.1.404) in early March that fixes one
PDB handle issue we finally found out. The site
http://www.microsoft.com/whdc/devtools/debugging/default.mspx does not
update the version, but if you click the link and upgrade, it should be
build 404.
If you still repro the problem from 6.11.1.404, please let us know and we
will look into this.
Thanks,
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Thursday, March 26, 2009 12:51 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Windbg still not releasing handle to .pdb
> As far as the conditions involved, I have no idea, other than to say that
> mine had to be different, as Ctrl+E was totally unknown to me until just
> now.
You mean you don’t debug your apps with WinDBG? For shame…
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Martin O’Brien” wrote in message
news:xxxxx@windbg…
> +1 as far as having seen with 6.11.1.402, and also as far as reporting it,
> though to be fair, I didn’t report it via the windbg alias, but I was told
> that the windbg folks already knew about it. I don’t really know what
> happened, but I guess that it doesn’t really matter either, as at least
> the ever dependable Snoone reported it.
>
> As far as the conditions involved, I have no idea, other than to say that
> mine had to be different, as Ctrl+E was totally unknown to me until just
> now.
>
> mm
>
>
>
>
>
>
>
>
> Scott Noone wrote:
>> I reported it last month, but I’m still hitting it frequently with the
>> latest available release…
>>
>> For me, it seems to be most evident when debugging applications launched
>> by WinDBG (Ctrl+E). Over the last couple of days I resorted to having
>> ProcessExplorer’s “search handle” dialog up so I can close the 1-4
>> outstanding handles without having to quit WinDBG between builds.
>>
>> -scott
>>
>
—
WINDBG 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
—
WINDBG 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