Indeed it does - dt, that is. It makes me happy as well.
Scott Noone wrote:
“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 > > -scott >
I’ve seen this - the disappearing - but it occurred in a pretty unusual circumstance, I think. I
had two instances of WinDbg open, both 1394, with channel==1 for the hypervisor and channel==2 for
the kernel, but on the target, I had inadvertently set hypervisorchannel==1 AND channel==1.
I haven’t looked in to it any further, but I’ll go check now, as maybe it’s not as unusual a
circumstance as I thought.
Thanks,
mm
Scott Noone wrote:
“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 > > -scott >
Ya, but then you are not re-booting.
You are new booting…
On Tue, Nov 25, 2008 at 1:21 PM, Joseph M. Newcomer
wrote:
> 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 < > 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@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 >
Sigh! Thanks! I just installed. I’ll rollback ASAP. MSFT - come on now, this
isnt good enough, not by half.
“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.
“Alexandru Carp” wrote in message news:xxxxx@windbg… > Hmm… I just use “.reload -u mydriver” before I rebuild. Is this broken > in this version as well ? > > Thanks, > Alex.
The specific circumstance in which I have observed it was loading the symbols for a UM app while debugging through the KM debugger. Even a full reload/unload cycle (.reload; .reload /u) was unable to persuade the 'Bag from releasing the pdb for the UM app, whether the app had exited or not. I had to close the handle with Process Explorer if I didn’t want to restart the /Bag.
This is the first version I can remember reverting from since I started using the 'Bag just after it went from 5.x to 1.0. And for me to call it “the 'Bag” instead of “windbg” (as I have for a long time) does not speak well to my regard for this particular version.
Phil – Philip D. Barila Seagate Technology LLC (720) 684-1842 As if I need to say it: Not speaking for Seagate.
