Any resolution to the locked PDB problem

Has there been any resolution to the locked PDB problem. This is
starting to get annoying…

–Mark

FWIW if you switch to 6.4, reload /u always will unload your pdb.
Otherwise as someone in this group suggested, load your pdb from another
location (local symstore, just a diff directory etc).

We’ve located one bug which causes this locking when source breakpoints
are used. The next debugger drop, which is currently planned to be a
beta-level drop, should release by the end of the year (or possibly
January depending on holiday schedules).

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mark J. Cariddi
Sent: Thursday, November 10, 2005 7:41 AM
To: Kernel Debugging Interest List
Subject: [windbg] Any resolution to the locked PDB problem

Has there been any resolution to the locked PDB problem. This is
starting to get annoying…

–Mark


You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

First of all, I’ll assume your driver is not unloadable, because if it is
unloadable, unloading will free the pdb.
Putting stuff in another directory, at least for me, is a bad idea - because
if the pdb and the binary do not match an exception will be throw as windbg
puts the int 3 for a break point the wrong place.

Failing that, just exit and restart windbg. Assuming you have a named
workspace for the driver, make a shortcut for the driver project that loads
this workspace, then it only takes a moment to do this - much faster than a
re-boot.

Note that there is no debugger I know of that will release the pdb with
somehow stopping the debug session.

Here what’s REALLY annoying: A checkbox that says “Don’t ask again” that
does nothing… please remove it or make it do something - I would be very
happy to set “Always save”

“Mark J. Cariddi” wrote in message news:xxxxx@windbg…
> Has there been any resolution to the locked PDB problem. This is
> starting to get annoying…
>
> --Mark
>

The “Don’t save” checkbox is only intended to work for a single execution of windbg. We’ll be changing it to make it permanent in an upcoming version.


From: xxxxx@lists.osr.com on behalf of jim
Sent: Sun 11/13/2005 10:38 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Any resolution to the locked PDB problem

First of all, I’ll assume your driver is not unloadable, because if it is
unloadable, unloading will free the pdb.
Putting stuff in another directory, at least for me, is a bad idea - because
if the pdb and the binary do not match an exception will be throw as windbg
puts the int 3 for a break point the wrong place.

Failing that, just exit and restart windbg. Assuming you have a named
workspace for the driver, make a shortcut for the driver project that loads
this workspace, then it only takes a moment to do this - much faster than a
re-boot.

Note that there is no debugger I know of that will release the pdb with
somehow stopping the debug session.

Here what’s REALLY annoying: A checkbox that says “Don’t ask again” that
does nothing… please remove it or make it do something - I would be very
happy to set “Always save”

“Mark J. Cariddi” wrote in message news:xxxxx@windbg…
> Has there been any resolution to the locked PDB problem. This is
> starting to get annoying…
>
> --Mark
>


You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

It doesn’t free pdb in windbg 6.5 upon unload.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of jim
Sent: Sunday, November 13, 2005 10:38 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Any resolution to the locked PDB problem

First of all, I’ll assume your driver is not unloadable, because if it
is unloadable, unloading will free the pdb.

Well … sometimes 6.5.003.7/8 gets petulant and will not free the PDB when
you use “.reload -u mydriver”. I can go through may builds and driver
reloads.


The personal opinion of
Gary G. Little

“Satya Das” wrote in message news:xxxxx@windbg…
It doesn’t free pdb in windbg 6.5 upon unload.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of jim
Sent: Sunday, November 13, 2005 10:38 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Any resolution to the locked PDB problem

First of all, I’ll assume your driver is not unloadable, because if it
is unloadable, unloading will free the pdb.