I don’t know of any command to change the title once you are in the
debugger. We can look at adding that.
Perhaps having an icon per target would be the thing. And then pass in
connection settings on the cmd line rather than the workspace.
The guys who run the labs here typically have around 40 machines hooked
up to 1 debugger. They usually have a batch file that launches the
debugger (kd in their case) against a given target with all the right
settings (port, sympath, etc…) The title bar is how they identify
different debugger sessions. Then people typically connect to kd with
Windbg via the network and debug.
-----Original Message-----
From: Gary Little [mailto:xxxxx@Broadstor.com]
Sent: Thursday, September 27, 2001 11:16 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: [winDbg] Only because it’s what I’m doing right
now …
But … I start WinDbg from an ICON, usually in the quick launch portion
of
the task bar, and not from a command line. Once in WinDbg I open one of
several workspaces depending on COM port and OS. I looked for a bang
command
to set the title bar but didn’t see any.
Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@broadstor.com
-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@windows.microsoft.com]
Sent: Thursday, September 27, 2001 9:56 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: [winDbg] Only because it’s what I’m doing right
now
…
That is a good idea. However I don’t think a change to do this would
give you any real advantage over what you can do now with the current
Windbg.
You can use the -T command line option when you start your windbg
session and give each Windbg instance a title that identifies it. Then
you can use the taskbar to switch between them.
-----Original Message-----
From: Gary Little [mailto:xxxxx@Broadstor.com]
Sent: Thursday, September 27, 2001 8:35 AM
To: Kernel Debugging Interest List
Subject: [windbg] [winDbg] Only because it’s what I’m doing right now
…
Nathan,
I am currently using both comports of my development system to debug 2
different targets. Usually, I am only working one target at a time, but
occasionally I work both targets using 2 instances of WinDbg. There are
times when it would be nice if I could stay in one instance of WinDbg,
but
have multiple KD session running with in it.
Barring that, maybe indicate on the minimized window on the horizontal
toolbar what type of session and port (“KD, COM1, FileName”).
Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@broadstor.com
You are currently subscribed to windbg as: xxxxx@microsoft.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: xxxxx@microsoft.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