Local kernel debugging with 6.0.7 on XP

Are there any known issues when using 6.0.7 on XP in a local kernel debug
situation? I have a machine here that merely reports back “Unable to get
address of debugger data list”. The symbols appear to be correct (starting
it with -n, no reports that it even LOOKS for any symbols.) I tried
“.reload” but that merely repeats this error. I’ve also run symchk to make
sure I have the right symbols - it reports that I have them for
ntoskrnl.exe.

Another machine I have here works fine with it.

Thoughts? Suggestions? Ideas?

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com http:</http:>

Hi Tony,

Are you using a symbol server? The problem I have encountered with
symbol server is that the debugger has difficulties to both use the
symbols on the symbol server and the local path for your own modules.

Best regards,
Marco.

Marco van Nieuwenhoven, QA Manager
ThunderStore B.V. - http:</http:> www.thunderstore.com
Phone: +31 (0)736 154 860, Fax: +31 (0) 736 121 830
mailto:xxxxx xxxxx@thunderstore.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Wednesday, March 20, 2002 7:20 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local kernel debugging with 6.0.7 on XP

Are there any known issues when using 6.0.7 on XP in a local kernel
debug situation? I have a machine here that merely reports back “Unable
to get address of debugger data list”. The symbols appear to be correct
(starting it with -n, no reports that it even LOOKS for any symbols.) I
tried “.reload” but that merely repeats this error. I’ve also run
symchk to make sure I have the right symbols - it reports that I have
them for ntoskrnl.exe.

Another machine I have here works fine with it.

Thoughts? Suggestions? Ideas?

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com


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

To unsubscribe send a blank email to %%email.unsub%%</mailto:xxxxx>

Marco,

Thanks for your suggestion.

As it turns out, you must set the /debug option in boot.ini even for local
debugging. The fact that it worked on my laptop (which has lots of memory)
and not on the machine I was using (hooked up to a projector that I was
using for the presentation) was fortuitous.

Of course, the solution was simple - I just started a server session on my
laptop and connected to it on the other computer (thus, I was running a
remote kernel debug session on a system doing local debugging!)

As for the symbol server, the “symchk” utility included in the Version 6.0.7
debugger is a terrific way to “seed” the symbol cache so that I have
everything I need (no need for the network). I have not observed the
debugger having problems mixing sources of symbols, however.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com http:

-----Original Message-----
From: ThunderStore - Marco van Nieuwenhoven [mailto:xxxxx@thunderstore.com]
Sent: Thursday, March 21, 2002 4:19 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP

Hi Tony,

Are you using a symbol server? The problem I have encountered with symbol
server is that the debugger has difficulties to both use the symbols on the
symbol server and the local path for your own modules.

Best regards,
Marco.

Marco van Nieuwenhoven, QA Manager
ThunderStore B.V. - http:</http:> www.thunderstore.com
Phone: +31 (0)736 154 860, Fax: +31 (0) 736 121 830
mailto:xxxxx xxxxx@thunderstore.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Wednesday, March 20, 2002 7:20 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local kernel debugging with 6.0.7 on XP
Are there any known issues when using 6.0.7 on XP in a local kernel debug
situation? I have a machine here that merely reports back “Unable to get
address of debugger data list”. The symbols appear to be correct (starting
it with -n, no reports that it even LOOKS for any symbols.) I tried
“.reload” but that merely repeats this error. I’ve also run symchk to make
sure I have the right symbols - it reports that I have them for
ntoskrnl.exe.

Another machine I have here works fine with it.

Thoughts? Suggestions? Ideas?

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com http:


You are currently subscribed to windbg as: xxxxx@thunderstore.com
To unsubscribe send a blank email to %%email.unsub%%

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

Hi Tony,

At the moment I have a problem debugging one of our InteroOp testing
combinations. We do kernel mode debugging on a 115200 serial connection
(and that is very slow!). So we tried to run dbgview.exe in client
server mode but in that situation we are missing quite a lot of debug
lines. The problem is that we cannot use WindowsXP for some InterOp
testing because the real BSOD only occurs on Win2K or NT. We also had an
idea on re-directing the info from dbgprint to a file on the harddisk
but then we have the problem that we have both the driver and the
service logging and having the risk that logging gets out of sync. Also
the other challenge is to write to a file from within the driver
itselves but we find that too tricky.

You just describe a server session on the laptop, do you use DbgView or
something else . …

grtx Marco.

Marco van Nieuwenhoven, QA Manager
ThunderStore B.V. - http:</http:> www.thunderstore.com
Phone: +31 (0)736 154 860, Fax: +31 (0) 736 121 830
mailto:xxxxx xxxxx@thunderstore.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Thursday, March 21, 2002 1:56 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP

Marco,

Thanks for your suggestion.

As it turns out, you must set the /debug option in boot.ini even for
local debugging. The fact that it worked on my laptop (which has lots
of memory) and not on the machine I was using (hooked up to a projector
that I was using for the presentation) was fortuitous.

Of course, the solution was simple - I just started a server session on
my laptop and connected to it on the other computer (thus, I was running
a remote kernel debug session on a system doing local debugging!)

As for the symbol server, the “symchk” utility included in the Version
6.0.7 debugger is a terrific way to “seed” the symbol cache so that I
have everything I need (no need for the network). I have not observed
the debugger having problems mixing sources of symbols, however.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: ThunderStore - Marco van Nieuwenhoven
[mailto:xxxxx@thunderstore.com]
Sent: Thursday, March 21, 2002 4:19 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP

Hi Tony,

Are you using a symbol server? The problem I have encountered with
symbol server is that the debugger has difficulties to both use the
symbols on the symbol server and the local path for your own modules.

Best regards,
Marco.

Marco van Nieuwenhoven, QA Manager
ThunderStore B.V. - http:</http:> www.thunderstore.com
Phone: +31 (0)736 154 860, Fax: +31 (0) 736 121 830
mailto:xxxxx xxxxx@thunderstore.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Wednesday, March 20, 2002 7:20 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local kernel debugging with 6.0.7 on XP
Are there any known issues when using 6.0.7 on XP in a local kernel
debug situation? I have a machine here that merely reports back “Unable
to get address of debugger data list”. The symbols appear to be correct
(starting it with -n, no reports that it even LOOKS for any symbols.) I
tried “.reload” but that merely repeats this error. I’ve also run
symchk to make sure I have the right symbols - it reports that I have
them for ntoskrnl.exe.

Another machine I have here works fine with it.

Thoughts? Suggestions? Ideas?

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com


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

To unsubscribe send a blank email to %%email.unsub%%

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

You are currently subscribed to windbg as: xxxxx@thunderstore.com
To unsubscribe send a blank email to %%email.unsub%%</mailto:xxxxx></mailto:xxxxx>

I’m running WinDBG (local) on an XP system. That will not work on NT or
W2K, so I fear that it will not solve your problem. Sorry!

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com http:

-----Original Message-----
From: ThunderStore - Marco van Nieuwenhoven [mailto:xxxxx@thunderstore.com]
Sent: Thursday, March 21, 2002 8:15 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP

Hi Tony,

At the moment I have a problem debugging one of our InteroOp testing
combinations. We do kernel mode debugging on a 115200 serial connection (and
that is very slow!). So we tried to run dbgview.exe in client server mode
but in that situation we are missing quite a lot of debug lines. The problem
is that we cannot use WindowsXP for some InterOp testing because the real
BSOD only occurs on Win2K or NT. We also had an idea on re-directing the
info from dbgprint to a file on the harddisk but then we have the problem
that we have both the driver and the service logging and having the risk
that logging gets out of sync. Also the other challenge is to write to a
file from within the driver itselves but we find that too tricky.

You just describe a server session on the laptop, do you use DbgView or
something else . …

grtx Marco.

Marco van Nieuwenhoven, QA Manager
ThunderStore B.V. - http:</http:> www.thunderstore.com
Phone: +31 (0)736 154 860, Fax: +31 (0) 736 121 830
mailto:xxxxx xxxxx@thunderstore.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Thursday, March 21, 2002 1:56 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP
Marco,

Thanks for your suggestion.

As it turns out, you must set the /debug option in boot.ini even for local
debugging. The fact that it worked on my laptop (which has lots of memory)
and not on the machine I was using (hooked up to a projector that I was
using for the presentation) was fortuitous.

Of course, the solution was simple - I just started a server session on my
laptop and connected to it on the other computer (thus, I was running a
remote kernel debug session on a system doing local debugging!)

As for the symbol server, the “symchk” utility included in the Version 6.0.7
debugger is a terrific way to “seed” the symbol cache so that I have
everything I need (no need for the network). I have not observed the
debugger having problems mixing sources of symbols, however.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com http:

-----Original Message-----
From: ThunderStore - Marco van Nieuwenhoven [mailto:xxxxx@thunderstore.com]
Sent: Thursday, March 21, 2002 4:19 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP

Hi Tony,

Are you using a symbol server? The problem I have encountered with symbol
server is that the debugger has difficulties to both use the symbols on the
symbol server and the local path for your own modules.

Best regards,
Marco.

Marco van Nieuwenhoven, QA Manager
ThunderStore B.V. - http:</http:> www.thunderstore.com
Phone: +31 (0)736 154 860, Fax: +31 (0) 736 121 830
mailto:xxxxx xxxxx@thunderstore.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Wednesday, March 20, 2002 7:20 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local kernel debugging with 6.0.7 on XP
Are there any known issues when using 6.0.7 on XP in a local kernel debug
situation? I have a machine here that merely reports back “Unable to get
address of debugger data list”. The symbols appear to be correct (starting
it with -n, no reports that it even LOOKS for any symbols.) I tried
“.reload” but that merely repeats this error. I’ve also run symchk to make
sure I have the right symbols - it reports that I have them for
ntoskrnl.exe.

Another machine I have here works fine with it.

Thoughts? Suggestions? Ideas?

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com http:


You are currently subscribed to windbg as: xxxxx@thunderstore.com
To unsubscribe send a blank email to %%email.unsub%%

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

You are currently subscribed to windbg as: xxxxx@thunderstore.com
To unsubscribe send a blank email to %%email.unsub%%

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

I was already afraid that was the case. Does anyone know if it is
possible to use an other UART (like the 16650) which can run on 4 times
115200Kb?

grtx Marco.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Thursday, March 21, 2002 2:24 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP

I’m running WinDBG (local) on an XP system. That will not work on NT or
W2K, so I fear that it will not solve your problem. Sorry!

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: ThunderStore - Marco van Nieuwenhoven
[mailto:xxxxx@thunderstore.com]
Sent: Thursday, March 21, 2002 8:15 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP

Hi Tony,

At the moment I have a problem debugging one of our InteroOp testing
combinations. We do kernel mode debugging on a 115200 serial connection
(and that is very slow!). So we tried to run dbgview.exe in client
server mode but in that situation we are missing quite a lot of debug
lines. The problem is that we cannot use WindowsXP for some InterOp
testing because the real BSOD only occurs on Win2K or NT. We also had an
idea on re-directing the info from dbgprint to a file on the harddisk
but then we have the problem that we have both the driver and the
service logging and having the risk that logging gets out of sync. Also
the other challenge is to write to a file from within the driver
itselves but we find that too tricky.

You just describe a server session on the laptop, do you use DbgView or
something else . …

grtx Marco.

Marco van Nieuwenhoven, QA Manager
ThunderStore B.V. - http:</http:> www.thunderstore.com
Phone: +31 (0)736 154 860, Fax: +31 (0) 736 121 830
mailto:xxxxx xxxxx@thunderstore.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Thursday, March 21, 2002 1:56 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP
Marco,

Thanks for your suggestion.

As it turns out, you must set the /debug option in boot.ini even for
local debugging. The fact that it worked on my laptop (which has lots
of memory) and not on the machine I was using (hooked up to a projector
that I was using for the presentation) was fortuitous.

Of course, the solution was simple - I just started a server session on
my laptop and connected to it on the other computer (thus, I was running
a remote kernel debug session on a system doing local debugging!)

As for the symbol server, the “symchk” utility included in the Version
6.0.7 debugger is a terrific way to “seed” the symbol cache so that I
have everything I need (no need for the network). I have not observed
the debugger having problems mixing sources of symbols, however.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: ThunderStore - Marco van Nieuwenhoven
[mailto:xxxxx@thunderstore.com]
Sent: Thursday, March 21, 2002 4:19 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Local kernel debugging with 6.0.7 on XP

Hi Tony,

Are you using a symbol server? The problem I have encountered with
symbol server is that the debugger has difficulties to both use the
symbols on the symbol server and the local path for your own modules.

Best regards,
Marco.

Marco van Nieuwenhoven, QA Manager
ThunderStore B.V. - http:</http:> www.thunderstore.com
Phone: +31 (0)736 154 860, Fax: +31 (0) 736 121 830
mailto:xxxxx xxxxx@thunderstore.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Wednesday, March 20, 2002 7:20 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local kernel debugging with 6.0.7 on XP
Are there any known issues when using 6.0.7 on XP in a local kernel
debug situation? I have a machine here that merely reports back “Unable
to get address of debugger data list”. The symbols appear to be correct
(starting it with -n, no reports that it even LOOKS for any symbols.) I
tried “.reload” but that merely repeats this error. I’ve also run
symchk to make sure I have the right symbols - it reports that I have
them for ntoskrnl.exe.

Another machine I have here works fine with it.

Thoughts? Suggestions? Ideas?

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com


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

To unsubscribe send a blank email to %%email.unsub%%

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

You are currently subscribed to windbg as: xxxxx@thunderstore.com
To unsubscribe send a blank email to %%email.unsub%%

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

You are currently subscribed to windbg as: xxxxx@thunderstore.com
To unsubscribe send a blank email to %%email.unsub%%</mailto:xxxxx></mailto:xxxxx>