]WinDbg] new beta 3.0

WINDBG
1

Well I tried it, and I am still watching it to tell me that it can’t verify
the timestamp after it caught a BSOD. From what I could tell there was
plenty of information being dumped, but I can’t look at it because it’s
still telling me it can’t verify the time stamp on every god damned source
module in the god damned system. This is rather important, since it EATS UP
RESOURCES and my system starts bitching about windows I need to close
because I’m running low on virtual memory, which slows things down even
further.

Not a very good first showing. :frowning: But it’s only a beta …

Gary

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

Buy more physical memory, and increase your pagefile size. Seriously.

I only have 256 MB here at work, and I only run out of VM when I use a
particularly buggy app that leaks VM like melting ice cream. I’ve never had
WinDBG cause that. I don’t think I’ve caught a BSOD with the new beta,
though, so maybe that’s the difference.

Phil

-----Original Message-----
From: Gary Little [mailto:xxxxx@Broadstor.com]
Sent: Monday, April 23, 2001 2:51 PM
To: Kernel Debugging Interest List
Subject: [windbg] ]WinDbg] new beta 3.0

Well I tried it, and I am still watching it to tell me that it can’t verify
the timestamp after it caught a BSOD. From what I could tell there was
plenty of information being dumped, but I can’t look at it because it’s
still telling me it can’t verify the time stamp on every god damned source
module in the god damned system. This is rather important, since it EATS UP
RESOURCES and my system starts bitching about windows I need to close
because I’m running low on virtual memory, which slows things down even
further.

Not a very good first showing. :frowning: But it’s only a beta …

Gary

You are currently subscribed to windbg as: xxxxx@intel.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

3

I’ve gotten some of those complaints, but they’re many fewer than they were
with v 2.0023.

James Antognini
IBM Research

Internet address – antognini@us.ibm.com
Notes address – James Antognini/Watson/xxxxx@IBMUS

Phone – external: 914-784-7258; tieline: 863-7258

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

4

Well, I’m waiting on the machine with 512 meg RAM and 20 gig HDD, but right
now I have work to do on 128 meg RAM. The point it I was hoping the time
stamp problem had been MOIDERED!!!

Gary

-----Original Message-----
From: Barila, Phil [mailto:xxxxx@intel.com]
Sent: Monday, April 23, 2001 2:57 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: ]WinDbg] new beta 3.0

Buy more physical memory, and increase your pagefile size.
Seriously.

I only have 256 MB here at work, and I only run out of VM
when I use a
particularly buggy app that leaks VM like melting ice cream.
I’ve never had
WinDBG cause that. I don’t think I’ve caught a BSOD with
the new beta,
though, so maybe that’s the difference.

Phil

-----Original Message-----
From: Gary Little [mailto:xxxxx@Broadstor.com]
Sent: Monday, April 23, 2001 2:51 PM
To: Kernel Debugging Interest List
Subject: [windbg] ]WinDbg] new beta 3.0

Well I tried it, and I am still watching it to tell me that
it can’t verify
the timestamp after it caught a BSOD. From what I could tell
there was
plenty of information being dumped, but I can’t look at it
because it’s
still telling me it can’t verify the time stamp on every god
damned source
module in the god damned system. This is rather important,
since it EATS UP
RESOURCES and my system starts bitching about windows I need
to close
because I’m running low on virtual memory, which slows
things down even
further.

Not a very good first showing. :frowning: But it’s only a beta …

Gary

You are currently subscribed to windbg as:
xxxxx@intel.com
To unsubscribe send a blank email to
leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to windbg as:
xxxxx@broadstor.com
To unsubscribe send a blank email to
leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

5

We will still print the timestamp warning message if the timestamp is
actually wrong (symbols doe snot match the image).

If you think you have the right symbols for the image and are still getting
the message, please let me know and we can look at it further.

-Andre

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

6

Andre,

I downloaded the ISO files for 2462 support and the OS when it was first
available for download. I would assume that the symbol files in the Support
ISO file were the correct files. The date on the files in …\Symbols\sys is
03/15/01, and the date on the drivers in %SystemRoot%\Sytem32/Drivers is
03/20/2001, with a few files still dated 03/15/01. I looked at the dates on
the HAL DLLs and the HAL PDBs, with the same results. Quite possibly the
symbol files are the culprit.

Now, I’m not bitching here, really, just letting you know you missed one
aspect of the problem, or the wrong symbol files were released.

Gary

-----Original Message-----
From: xxxxx@microsoft.com [mailto:xxxxx@microsoft.com]
Sent: Monday, April 23, 2001 5:00 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: ]WinDbg] new beta 3.0

We will still print the timestamp warning message if the
timestamp is
actually wrong (symbols doe snot match the image).

If you think you have the right symbols for the image and
are still getting
the message, please let me know and we can look at it
further.

-Andre

You are currently subscribed to windbg as:
xxxxx@broadstor.com
To unsubscribe send a blank email to
leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

7

Sounds like the symbols are wrong.

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com