WinDbg 6.10.3.233 doesn't close PDB files

New WinDbg version 6.10.3.233 doesn’t close PDB files when I use “.reboot” command. Therefore I’m not able to build new SYS+PDB files unless I close the file handle from Process Explorer.

“John Smith” wrote in message news:xxxxx@windbg…
> New WinDbg version 6.10.3.233 doesn’t close PDB files when I use “.reboot”
> command.
> Therefore I’m not able to build new SYS+PDB files unless I close the file
> handle from Process
> Explorer.

I’ve observed the same behavior. It’s annoying enough that I reverted to
6.9. YMMV.

Phil

Philip D. Barila
Seagate Technology LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.

I think I speak for all of us, when I say:

Not *this* again?

  • S

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of John Smith
Sent: Tuesday, November 25, 2008 6:21 AM
To: Kernel Debugging Interest List
Subject: [windbg] WinDbg 6.10.3.233 doesn’t close PDB files

New WinDbg version 6.10.3.233 doesn’t close PDB files when I use “.reboot” command. Therefore I’m not able to build new SYS+PDB files unless I close the file handle from Process Explorer.

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

Good point - this has been discussed.
Not releasing the files on reboot is a good thing. Then it does not have to
reload them.
When I need to rebuild, I just close windbg. That always works.

On Tue, Nov 25, 2008 at 10:37 AM, Skywing wrote:

> I think I speak for all of us, when I say:
>
>
>
> Not this again?
>
>
>
> - S
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *John Smith
> Sent: Tuesday, November 25, 2008 6:21 AM
> To: Kernel Debugging Interest List
> Subject: [windbg] WinDbg 6.10.3.233 doesn’t close PDB files
>
>
>
> New WinDbg version 6.10.3.233 doesn’t close PDB files when I use “.reboot”
> command. Therefore I’m not able to build new SYS+PDB files unless I close
> the file handle from Process Explorer.
>
>
> — You are currently subscribed to windbg as: xxxxx@valhallalegends.comTo unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
> —
> You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
>
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

“Jim Donelson” wrote in message news:xxxxx@windbg…
> Good point - this has been discussed.
> Not releasing the files on reboot is a good thing. Then it does not have
> to
> reload them.

This is patently wrong. The next time the debugger reconnects, the OS may
be different. It might even be a different system altogether.

> When I need to rebuild, I just close windbg. That always works.

So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
most efficient approach to dealing with that particular problem …

Phil

Philip D. Barila
Seagate Technology LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.

I was more speaking of the standpoint of ?not this highly annoying bug regressing yet again?.

To add to what Phil said, it also sucks if you?re doing remote debugging.

  • S

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Jim Donelson
Sent: Tuesday, November 25, 2008 11:29 AM
To: Kernel Debugging Interest List
Subject: Re: [windbg] WinDbg 6.10.3.233 doesn’t close PDB files

Good point - this has been discussed.
Not releasing the files on reboot is a good thing. Then it does not have to reload them.
When I need to rebuild, I just close windbg. That always works.
On Tue, Nov 25, 2008 at 10:37 AM, Skywing > wrote:

I think I speak for all of us, when I say:

Not this again?

- S

From: xxxxx@lists.osr.commailto:xxxxx [mailto:xxxxx@lists.osr.commailto:xxxxx] On Behalf Of John Smith
Sent: Tuesday, November 25, 2008 6:21 AM
To: Kernel Debugging Interest List
Subject: [windbg] WinDbg 6.10.3.233http: doesn’t close PDB files

New WinDbg version 6.10.3.233http: doesn’t close PDB files when I use “.reboot” command. Therefore I’m not able to build new SYS+PDB files unless I close the file handle from Process Explorer.

— You are currently subscribed to windbg as: xxxxx@valhallalegends.commailto:xxxxx To unsubscribe send a blank email to xxxxx@lists.osr.commailto:xxxxx


You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.commailto:xxxxx

— You are currently subscribed to windbg as: xxxxx@valhallalegends.com To unsubscribe send a blank email to xxxxx@lists.osr.com</mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></http:></http:></mailto:xxxxx></mailto:xxxxx>

>This is patently wrong. The next time the debugger reconnects, the *OS*
may

be different. It might even be a different system altogether.

Interesting, you change the os between reboots. How is that done?

So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
most efficient approach to dealing with that particular problem …

I thought the issue was re-building the driver, normally you reboot so you
can re-build and re-load, or because you raised an exception in the kernel
and found the issue, so now you need to re-boot and re-build.

On Tue, Nov 25, 2008 at 11:53 AM, Philip D. Barila <
xxxxx@seagate.com> wrote:

“Jim Donelson” wrote in message news:xxxxx@windbg…
> > Good point - this has been discussed.
> > Not releasing the files on reboot is a good thing. Then it does not have
> > to
> > reload them.
>
> This is patently wrong. The next time the debugger reconnects, the OS
> may
> be different. It might even be a different system altogether.
>
> > When I need to rebuild, I just close windbg. That always works.
>
> So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
> most efficient approach to dealing with that particular problem …
>
> Phil
> –
> Philip D. Barila
> Seagate Technology LLC
> (720) 684-1842
> As if I need to say it: Not speaking for Seagate.
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@jimdonelson.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

Dual boot?

  • S

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Jim Donelson
Sent: Tuesday, November 25, 2008 12:00 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] WinDbg 6.10.3.233 doesn’t close PDB files

This is patently wrong. The next time the debugger reconnects, the *OS* may
be different. It might even be a different system altogether.

Interesting, you change the os between reboots. How is that done?

So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
most efficient approach to dealing with that particular problem …

I thought the issue was re-building the driver, normally you reboot so you can re-build and re-load, or because you raised an exception in the kernel and found the issue, so now you need to re-boot and re-build.

On Tue, Nov 25, 2008 at 11:53 AM, Philip D. Barila > wrote:
“Jim Donelson” > wrote in message news:xxxxx@windbg…
> Good point - this has been discussed.
> Not releasing the files on reboot is a good thing. Then it does not have
> to
> reload them.
This is patently wrong. The next time the debugger reconnects, the OS may
be different. It might even be a different system altogether.

> When I need to rebuild, I just close windbg. That always works.
So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
most efficient approach to dealing with that particular problem …

Phil

Philip D. Barila
Seagate Technology LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.


You are currently subscribed to windbg as: xxxxx@jimdonelson.commailto:xxxxx
To unsubscribe send a blank email to xxxxx@lists.osr.commailto:xxxxx

— You are currently subscribed to windbg as: xxxxx@valhallalegends.com To unsubscribe send a blank email to xxxxx@lists.osr.com</mailto:xxxxx></mailto:xxxxx>

I suppose, but you have to admit, in practice the term re-boot implies “boot
again the system system I had last booted”.
If you boot “something else” then it really isn’t a re-boot. It’s a
new-boot.

On Tue, Nov 25, 2008 at 12:03 PM, Skywing wrote:

> Dual boot?
>
>
>
> - S
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *Jim Donelson
> Sent: Tuesday, November 25, 2008 12:00 PM
> To: Kernel Debugging Interest List
> Subject: Re: [windbg] WinDbg 6.10.3.233 doesn’t close PDB files
>
>
>
> >This is patently wrong. The next time the debugger reconnects, the OS
> may
> >be different. It might even be a different system altogether.
>
> Interesting, you change the os between reboots. How is that done?
>
> >So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
> >most efficient approach to dealing with that particular problem …
>
> I thought the issue was re-building the driver, normally you reboot so you
> can re-build and re-load, or because you raised an exception in the kernel
> and found the issue, so now you need to re-boot and re-build.
>
>
> On Tue, Nov 25, 2008 at 11:53 AM, Philip D. Barila <
> xxxxx@seagate.com> wrote:
>
> “Jim Donelson” wrote in message news:xxxxx@windbg…
>
> > Good point - this has been discussed.
> > Not releasing the files on reboot is a good thing. Then it does not have
> > to
> > reload them.
>
> This is patently wrong. The next time the debugger reconnects, the OS
> may
> be different. It might even be a different system altogether.
>
>
> > When I need to rebuild, I just close windbg. That always works.
>
> So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
> most efficient approach to dealing with that particular problem …
>
>
> Phil
> –
> Philip D. Barila
> Seagate Technology LLC
> (720) 684-1842
> As if I need to say it: Not speaking for Seagate.
>
>
>
> —
>
> You are currently subscribed to windbg as: xxxxx@jimdonelson.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
> — You are currently subscribed to windbg as: xxxxx@valhallalegends.comTo unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
> —
> You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
>
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

Dual boot, or swappable disks. I have a test system which at a given moment
of the day, may have anyting from NT4.0RTM upto Win7 on it, and no I do not
expect to close WinDBG to reboot.


Don Burn (MVP, Windows DDK)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

“Skywing” wrote in message
news:xxxxx@windbg…
Dual boot?

- S

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jim Donelson
Sent: Tuesday, November 25, 2008 12:00 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] WinDbg 6.10.3.233 doesn’t close PDB files

>This is patently wrong. The next time the debugger reconnects, the OS
>may
>be different. It might even be a different system altogether.

Interesting, you change the os between reboots. How is that done?

>So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
>most efficient approach to dealing with that particular problem …

I thought the issue was re-building the driver, normally you reboot so you
can re-build and re-load, or because you raised an exception in the kernel
and found the issue, so now you need to re-boot and re-build.

On Tue, Nov 25, 2008 at 11:53 AM, Philip D. Barila
> wrote:
“Jim Donelson” > wrote in
message news:xxxxx@windbg…
> Good point - this has been discussed.
> Not releasing the files on reboot is a good thing. Then it does not have
> to
> reload them.
This is patently wrong. The next time the debugger reconnects, the OS may
be different. It might even be a different system altogether.

> When I need to rebuild, I just close windbg. That always works.
So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
most efficient approach to dealing with that particular problem …

Phil

Philip D. Barila
Seagate Technology LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.


You are currently subscribed to windbg as:
xxxxx@jimdonelson.commailto:xxxxx
To unsubscribe send a blank email to
xxxxx@lists.osr.commailto:xxxxx

— You are currently subscribed to windbg as: xxxxx@valhallalegends.com
To unsubscribe send a blank email to xxxxx@lists.osr.com</mailto:xxxxx></mailto:xxxxx>

Well, I guess if you are using .10 and need to re-build, you will be.
For me, closing windbg to re-build is such a non-issue. If you have a
shortcut with all your parameters set up, it is nothing to do that.

Has anyone found any other new noteworthy “features” ?

On Tue, Nov 25, 2008 at 12:22 PM, Don Burn wrote:

> Dual boot, or swappable disks. I have a test system which at a given
> moment
> of the day, may have anyting from NT4.0RTM upto Win7 on it, and no I do not
> expect to close WinDBG to reboot.
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
> Remove StopSpam to reply
>
>
>
> “Skywing” wrote in message
> news:xxxxx@windbg…
> Dual boot?
>
> - S
>
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Jim Donelson
> Sent: Tuesday, November 25, 2008 12:00 PM
> To: Kernel Debugging Interest List
> Subject: Re: [windbg] WinDbg 6.10.3.233 doesn’t close PDB files
>
> >This is patently wrong. The next time the debugger reconnects, the OS
> >may
> >be different. It might even be a different system altogether.
>
> Interesting, you change the os between reboots. How is that done?
>
> >So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
> >most efficient approach to dealing with that particular problem …
>
> I thought the issue was re-building the driver, normally you reboot so you
> can re-build and re-load, or because you raised an exception in the kernel
> and found the issue, so now you need to re-boot and re-build.
>
>
> On Tue, Nov 25, 2008 at 11:53 AM, Philip D. Barila
> > wrote:
> “Jim Donelson” > wrote in
> message news:xxxxx@windbg…
> > Good point - this has been discussed.
> > Not releasing the files on reboot is a good thing. Then it does not have
> > to
> > reload them.
> This is patently wrong. The next time the debugger reconnects, the OS
> may
> be different. It might even be a different system altogether.
>
> > When I need to rebuild, I just close windbg. That always works.
> So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
> most efficient approach to dealing with that particular problem …
>
> Phil
> –
> Philip D. Barila
> Seagate Technology LLC
> (720) 684-1842
> As if I need to say it: Not speaking for Seagate.
>
>
>
> —
> You are currently subscribed to windbg as:
> xxxxx@jimdonelson.commailto:xxxxx
> To unsubscribe send a blank email to
> xxxxx@lists.osr.commailto:xxxxx> >
>
> — You are currently subscribed to windbg as: xxxxx@valhallalegends.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@jimdonelson.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
></mailto:xxxxx></mailto:xxxxx>

Try this on a remote debug environment, shutting down then restarting WinDBG
when your customer is 3000 miles away makes this an unusable revision. Add
to the fact that as far as I can determine, everything they broke in the
last 3 revs prior to this as far as kernel debugging are still broken, means
I have removed this one from my system.


Don Burn (MVP, Windows DDK)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

“Jim Donelson” wrote in message news:xxxxx@windbg…
> Well, I guess if you are using .10 and need to re-build, you will be.
> For me, closing windbg to re-build is such a non-issue. If you have a
> shortcut with all your parameters set up, it is nothing to do that.
>
> Has anyone found any other new noteworthy “features” ?
>
> On Tue, Nov 25, 2008 at 12:22 PM, Don Burn wrote:
>
>> Dual boot, or swappable disks. I have a test system which at a given
>> moment
>> of the day, may have anyting from NT4.0RTM upto Win7 on it, and no I do
>> not
>> expect to close WinDBG to reboot.
>>
>>
>> –
>> Don Burn (MVP, Windows DDK)
>> Windows Filesystem and Driver Consulting
>> Website: http://www.windrvr.com
>> Blog: http://msmvps.com/blogs/WinDrvr
>> Remove StopSpam to reply
>>
>>
>>
>> “Skywing” wrote in message
>> news:xxxxx@windbg…
>> Dual boot?
>>
>> - S
>>
>> From: xxxxx@lists.osr.com
>> [mailto:xxxxx@lists.osr.com] On Behalf Of Jim Donelson
>> Sent: Tuesday, November 25, 2008 12:00 PM
>> To: Kernel Debugging Interest List
>> Subject: Re: [windbg] WinDbg 6.10.3.233 doesn’t close PDB files
>>
>> >This is patently wrong. The next time the debugger reconnects, the OS
>> >may
>> >be different. It might even be a different system altogether.
>>
>> Interesting, you change the os between reboots. How is that done?
>>
>> >So does rebooting the system to stop a runaway app. Doesn’t mean it’s
>> >the
>> >most efficient approach to dealing with that particular problem …
>>
>> I thought the issue was re-building the driver, normally you reboot so
>> you
>> can re-build and re-load, or because you raised an exception in the
>> kernel
>> and found the issue, so now you need to re-boot and re-build.
>>
>>
>> On Tue, Nov 25, 2008 at 11:53 AM, Philip D. Barila
>> > wrote:
>> “Jim Donelson” > wrote in
>> message news:xxxxx@windbg…
>> > Good point - this has been discussed.
>> > Not releasing the files on reboot is a good thing. Then it does not
>> > have
>> > to
>> > reload them.
>> This is patently wrong. The next time the debugger reconnects, the OS
>> may
>> be different. It might even be a different system altogether.
>>
>> > When I need to rebuild, I just close windbg. That always works.
>> So does rebooting the system to stop a runaway app. Doesn’t mean it’s
>> the
>> most efficient approach to dealing with that particular problem …
>>
>> Phil
>> –
>> Philip D. Barila
>> Seagate Technology LLC
>> (720) 684-1842
>> As if I need to say it: Not speaking for Seagate.
>>
>>
>>
>> —
>> You are currently subscribed to windbg as:
>> xxxxx@jimdonelson.commailto:xxxxx
>> To unsubscribe send a blank email to
>> xxxxx@lists.osr.commailto:xxxxx>> >
>>
>> — You are currently subscribed to windbg as:
>> xxxxx@valhallalegends.com
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>
>>
>> —
>> You are currently subscribed to windbg as: xxxxx@jimdonelson.com
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
></mailto:xxxxx></mailto:xxxxx>

See below…


From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jim Donelson
Sent: Tuesday, November 25, 2008 12:00 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] WinDbg 6.10.3.233 doesn’t close PDB files

This is patently wrong. The next time the debugger reconnects, the *OS*
may
be different. It might even be a different system altogether.

Interesting, you change the os between reboots. How is that done?
****
By the most trivial of techniques. Selecting a different operating system
in the boot-time menu.
*****

So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
most efficient approach to dealing with that particular problem …

I thought the issue was re-building the driver, normally you reboot so you
can re-build and re-load, or because you raised an exception in the kernel
and found the issue, so now you need to re-boot and re-build.
****
Very often the problem in a driver does not require a reboot; just
unplugging the device and then plugging the device back in again. PnP will
unload the driver when it is unplugged and reload the driver when it detects
the device, and in between you do the rebuild. If you have enabled the
dynamic download (“map file”) capability in WinDbg, it will download the new
driver from the connected development machine with no effort on your part.
In fact, one of the great motivators for building robust drivers is that
even when they are wrong, all IRPs get completed anyway, so the driver is
always in a stable and recoverable state. Once my students get beyond the
“oh, it blue-screened” stage of development, they can usually use this
technique and only need to reboot the test machine infrequently.
joe
*****

On Tue, Nov 25, 2008 at 11:53 AM, Philip D. Barila
wrote:
“Jim Donelson” wrote in message news:xxxxx@windbg…
> Good point - this has been discussed.
> Not releasing the files on reboot is a good thing. Then it does not have
> to
> reload them.
This is patently wrong. The next time the debugger reconnects, the OS may
be different. It might even be a different system altogether.

> When I need to rebuild, I just close windbg. That always works.
So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
most efficient approach to dealing with that particular problem …

Phil

Philip D. Barila
Seagate Technology LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.


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

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

This message has been scanned for viruses and
dangerous content by http:</http:> MailScanner, and is
believed to be clean.

Hmm… I just use “.reload -u mydriver” before I rebuild. Is this broken in this version as well ?

Thanks,
Alex.

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Joseph M. Newcomer
Sent: Tuesday, November 25, 2008 10:21 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] WinDbg 6.10.3.233 doesn’t close PDB files

See below…


From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Jim Donelson
Sent: Tuesday, November 25, 2008 12:00 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] WinDbg 6.10.3.233 doesn’t close PDB files

This is patently wrong. The next time the debugger reconnects, the *OS* may
be different. It might even be a different system altogether.

Interesting, you change the os between reboots. How is that done?
****
By the most trivial of techniques. Selecting a different operating system in the boot-time menu.
*****

So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
most efficient approach to dealing with that particular problem …

I thought the issue was re-building the driver, normally you reboot so you can re-build and re-load, or because you raised an exception in the kernel and found the issue, so now you need to re-boot and re-build.
****
Very often the problem in a driver does not require a reboot; just unplugging the device and then plugging the device back in again. PnP will unload the driver when it is unplugged and reload the driver when it detects the device, and in between you do the rebuild. If you have enabled the dynamic download (“map file”) capability in WinDbg, it will download the new driver from the connected development machine with no effort on your part.
In fact, one of the great motivators for building robust drivers is that even when they are wrong, all IRPs get completed anyway, so the driver is always in a stable and recoverable state. Once my students get beyond the “oh, it blue-screened” stage of development, they can usually use this technique and only need to reboot the test machine infrequently.
joe
*****

On Tue, Nov 25, 2008 at 11:53 AM, Philip D. Barila > wrote:
“Jim Donelson” > wrote in message news:xxxxx@windbg…
> Good point - this has been discussed.
> Not releasing the files on reboot is a good thing. Then it does not have
> to
> reload them.
This is patently wrong. The next time the debugger reconnects, the OS may
be different. It might even be a different system altogether.

> When I need to rebuild, I just close windbg. That always works.
So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
most efficient approach to dealing with that particular problem …

Phil

Philip D. Barila
Seagate Technology LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.


You are currently subscribed to windbg as: xxxxx@jimdonelson.commailto:xxxxx
To unsubscribe send a blank email to xxxxx@lists.osr.commailto:xxxxx

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

This message has been scanned for viruses and
dangerous content by MailScannerhttp:</http:>, and is
believed to be clean.


You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com</mailto:xxxxx></mailto:xxxxx>

But it has dockable windows! Isn’t that an *improvement*? (It is better to
add features than fix bugs, and if a few new bugs creep in, so what, it has
cool new features…like the ability to have your command window sitting on
TOP of the modal dialog that is hanging WinDbg. Isn’t this what we always
needed?)

For teaching, I use a fairly old version of WinDbg, because it is fairly
robust. I don’t use the newer versions because they have proven to be quite
buggy. Even then, I tell my students that part of the role of the
instructor is to teach them how to roll their eyes and say, in a resigned
tone, “Well, it IS WinDbg…”
joe

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Tuesday, November 25, 2008 12:36 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] WinDbg 6.10.3.233 doesn’t close PDB files

Try this on a remote debug environment, shutting down then restarting WinDBG

when your customer is 3000 miles away makes this an unusable revision. Add

to the fact that as far as I can determine, everything they broke in the
last 3 revs prior to this as far as kernel debugging are still broken, means

I have removed this one from my system.


Don Burn (MVP, Windows DDK)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

“Jim Donelson” wrote in message news:xxxxx@windbg…
> Well, I guess if you are using .10 and need to re-build, you will be.
> For me, closing windbg to re-build is such a non-issue. If you have a
> shortcut with all your parameters set up, it is nothing to do that.
>
> Has anyone found any other new noteworthy “features” ?
>
> On Tue, Nov 25, 2008 at 12:22 PM, Don Burn wrote:
>
>> Dual boot, or swappable disks. I have a test system which at a given
>> moment
>> of the day, may have anyting from NT4.0RTM upto Win7 on it, and no I do
>> not
>> expect to close WinDBG to reboot.
>>
>>
>> –
>> Don Burn (MVP, Windows DDK)
>> Windows Filesystem and Driver Consulting
>> Website: http://www.windrvr.com
>> Blog: http://msmvps.com/blogs/WinDrvr
>> Remove StopSpam to reply
>>
>>
>>
>> “Skywing” wrote in message
>> news:xxxxx@windbg…
>> Dual boot?
>>
>> - S
>>
>> From: xxxxx@lists.osr.com
>> [mailto:xxxxx@lists.osr.com] On Behalf Of Jim Donelson
>> Sent: Tuesday, November 25, 2008 12:00 PM
>> To: Kernel Debugging Interest List
>> Subject: Re: [windbg] WinDbg 6.10.3.233 doesn’t close PDB files
>>
>> >This is patently wrong. The next time the debugger reconnects, the OS
>> >may
>> >be different. It might even be a different system altogether.
>>
>> Interesting, you change the os between reboots. How is that done?
>>
>> >So does rebooting the system to stop a runaway app. Doesn’t mean it’s
>> >the
>> >most efficient approach to dealing with that particular problem …
>>
>> I thought the issue was re-building the driver, normally you reboot so
>> you
>> can re-build and re-load, or because you raised an exception in the
>> kernel
>> and found the issue, so now you need to re-boot and re-build.
>>
>>
>> On Tue, Nov 25, 2008 at 11:53 AM, Philip D. Barila
>> > wrote:
>> “Jim Donelson” > wrote in
>> message news:xxxxx@windbg…
>> > Good point - this has been discussed.
>> > Not releasing the files on reboot is a good thing. Then it does not
>> > have
>> > to
>> > reload them.
>> This is patently wrong. The next time the debugger reconnects, the OS
>> may
>> be different. It might even be a different system altogether.
>>
>> > When I need to rebuild, I just close windbg. That always works.
>> So does rebooting the system to stop a runaway app. Doesn’t mean it’s
>> the
>> most efficient approach to dealing with that particular problem …
>>
>> Phil
>> –
>> Philip D. Barila
>> Seagate Technology LLC
>> (720) 684-1842
>> As if I need to say it: Not speaking for Seagate.
>>
>>
>>
>> —
>> You are currently subscribed to windbg as:
>> xxxxx@jimdonelson.commailto:xxxxx
>> To unsubscribe send a blank email to
>>
xxxxx@lists.osr.commailto:xxxxx>> >
>>
>> — You are currently subscribed to windbg as:
>> xxxxx@valhallalegends.com
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>
>>
>> —
>> You are currently subscribed to windbg as: xxxxx@jimdonelson.com
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>


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


This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.</mailto:xxxxx></mailto:xxxxx>

Hello Joseph,

* On Tue, Nov 25, 2008 at 01:32:19PM -0500 Joseph M. Newcomer wrote:

For teaching, I use a fairly old version of WinDbg, because it is fairly
robust.

May I ask you (or others here) which one you refer to as being fairly
robust? I would be very interested in the opinions of others.

I, for myself, have several on my machine. However, I am using
6.4.0007.0 rather frequently, and the newer ones are used very seldom.

Regards,
Spiro.


Spiro R. Trikaliotis http://opencbm.sf.net/
http://www.trikaliotis.net/ http://www.viceteam.org/

I use 6.0.17.0 for teaching. I tend not to upgrade very often after I had a
total meltdown with a disastrous earlier (pre-rewrite) version of WinDbg
(the only thing that saved me was that it was an on-site course, and they
had Soft-ICE. That won’t happen again). So I have little motivation to
move from a version that pretty much works.
joe

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Spiro Trikaliotis
Sent: Tuesday, November 25, 2008 2:01 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] WinDbg 6.10.3.233 doesn’t close PDB files

Hello Joseph,

* On Tue, Nov 25, 2008 at 01:32:19PM -0500 Joseph M. Newcomer wrote:

For teaching, I use a fairly old version of WinDbg, because it is fairly
robust.

May I ask you (or others here) which one you refer to as being fairly
robust? I would be very interested in the opinions of others.

I, for myself, have several on my machine. However, I am using
6.4.0007.0 rather frequently, and the newer ones are used very seldom.

Regards,
Spiro.


Spiro R. Trikaliotis http://opencbm.sf.net/
http://www.trikaliotis.net/ http://www.viceteam.org/


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


This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

This behavior doesn’t seem useful to me (keeping everything loaded), but what I find most troubling
about it is that they just make fundamental changes like this all the time, and almost always do so
without telling anyone or even just documenting it. I mean, surely they must know that this is not
going to be everyone’s cup of tea, so I why not go for consistency? Lack of consistency might be
the hallmark of WinDbg.

Just my two cents,

mm

Joseph M. Newcomer wrote:

I use 6.0.17.0 for teaching. I tend not to upgrade very often after I had a
total meltdown with a disastrous earlier (pre-rewrite) version of WinDbg
(the only thing that saved me was that it was an on-site course, and they
had Soft-ICE. That won’t happen again). So I have little motivation to
move from a version that pretty much works.
joe

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Spiro Trikaliotis
Sent: Tuesday, November 25, 2008 2:01 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] WinDbg 6.10.3.233 doesn’t close PDB files

Hello Joseph,

* On Tue, Nov 25, 2008 at 01:32:19PM -0500 Joseph M. Newcomer wrote:

> For teaching, I use a fairly old version of WinDbg, because it is fairly
> robust.

May I ask you (or others here) which one you refer to as being fairly
robust? I would be very interested in the opinions of others.

I, for myself, have several on my machine. However, I am using
6.4.0007.0 rather frequently, and the newer ones are used very seldom.

Regards,
Spiro.

“Jim Donelson” wrote in message news:xxxxx@windbg…
>Has anyone found any other new noteworthy “features” ?

I’m struggling with the issue someone reported last week where WinDBG just
disappears while the target is booting. Not sure what it is yet but it just
terminates while in the waiting to connect state. Hopefully I’ll have time
later for a better bug report.

On the good side, dt now accepts wildcards again which makes me supremely
happy.

* On Tue, Nov 25, 2008 at 01:32:19PM -0500 Joseph M. Newcomer wrote:
> For teaching, I use a fairly old version of WinDbg, because it is fairly
> robust.

I always foist the latest and greatest on my students. I figure it’s better
for them to learn what’s user error and what’s the 'Bag in the lab
environment where they have moral support :slight_smile:

-scott


Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Jim Donelson” wrote in message news:xxxxx@windbg…
Well, I guess if you are using .10 and need to re-build, you will be.
For me, closing windbg to re-build is such a non-issue. If you have a
shortcut with all your parameters set up, it is nothing to do that.

Has anyone found any other new noteworthy “features” ?

On Tue, Nov 25, 2008 at 12:22 PM, Don Burn wrote:

Dual boot, or swappable disks. I have a test system which at a given moment
of the day, may have anyting from NT4.0RTM upto Win7 on it, and no I do not
expect to close WinDBG to reboot.


Don Burn (MVP, Windows DDK)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

“Skywing” wrote in message
news:xxxxx@windbg…
Dual boot?

- S

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jim Donelson
Sent: Tuesday, November 25, 2008 12:00 PM

To: Kernel Debugging Interest List

Subject: Re: [windbg] WinDbg 6.10.3.233 doesn’t close PDB files

>This is patently wrong. The next time the debugger reconnects, the OS
>may
>be different. It might even be a different system altogether.

Interesting, you change the os between reboots. How is that done?

>So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
>most efficient approach to dealing with that particular problem …

I thought the issue was re-building the driver, normally you reboot so you
can re-build and re-load, or because you raised an exception in the kernel
and found the issue, so now you need to re-boot and re-build.

On Tue, Nov 25, 2008 at 11:53 AM, Philip D. Barila

> wrote:
“Jim Donelson” > wrote in

message news:xxxxx@windbg…
> Good point - this has been discussed.
> Not releasing the files on reboot is a good thing. Then it does not have
> to
> reload them.
This is patently wrong. The next time the debugger reconnects, the OS may
be different. It might even be a different system altogether.

> When I need to rebuild, I just close windbg. That always works.
So does rebooting the system to stop a runaway app. Doesn’t mean it’s the
most efficient approach to dealing with that particular problem …

Phil

Philip D. Barila
Seagate Technology LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.


You are currently subscribed to windbg as:

xxxxx@jimdonelson.commailto:xxxxx

To unsubscribe send a blank email to

xxxxx@lists.osr.commailto:xxxxx

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



You are currently subscribed to windbg as: xxxxx@jimdonelson.com

To unsubscribe send a blank email to xxxxx@lists.osr.com</mailto:xxxxx></mailto:xxxxx>

Forgot something - even better, make it optional and document it. Of course, optional and msft are
kind of orthogonal.

mm

Martin O’Brien wrote:

This behavior doesn’t seem useful to me (keeping everything loaded), but
what I find most troubling about it is that they just make fundamental
changes like this all the time, and almost always do so without telling
anyone or even just documenting it. I mean, surely they must know that
this is not going to be everyone’s cup of tea, so I why not go for
consistency? Lack of consistency might be the hallmark of WinDbg.

Just my two cents,

mm

Joseph M. Newcomer wrote:
> I use 6.0.17.0 for teaching. I tend not to upgrade very often after I
> had a
> total meltdown with a disastrous earlier (pre-rewrite) version of WinDbg
> (the only thing that saved me was that it was an on-site course, and they
> had Soft-ICE. That won’t happen again). So I have little motivation to
> move from a version that pretty much works.
> joe
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Spiro Trikaliotis
> Sent: Tuesday, November 25, 2008 2:01 PM
> To: Kernel Debugging Interest List
> Subject: Re: [windbg] WinDbg 6.10.3.233 doesn’t close PDB files
>
> Hello Joseph,
>
> * On Tue, Nov 25, 2008 at 01:32:19PM -0500 Joseph M. Newcomer wrote:
>
>> For teaching, I use a fairly old version of WinDbg, because it is fairly
>> robust.
>
> May I ask you (or others here) which one you refer to as being fairly
> robust? I would be very interested in the opinions of others.
>
> I, for myself, have several on my machine. However, I am using
> 6.4.0007.0 rather frequently, and the newer ones are used very seldom.
>
> Regards,
> Spiro.
>