hi all,
I am using windbg version 6.4. I connect to COM2 of the machine at 19200 bauds.
I observe that initially when it hits a break point the debugger is
very slow. It takes ages to load the symbols and then another
millenium to execute the first command I type, is there a way to sped
up this. Typically around 10 minutes is taken to do all this. and
during that time my machine virtually becomes unresponsive. I have a
P-IV as a debugger with 256 megs and windows 2kSP4.
–
Try running at a higher baudrate. 115200 usually works for me.
-scott
–
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Developer” wrote in message news:xxxxx@windbg…
hi all,
I am using windbg version 6.4. I connect to COM2 of the machine at 19200
bauds.
I observe that initially when it hits a break point the debugger is
very slow. It takes ages to load the symbols and then another
millenium to execute the first command I type, is there a way to sped
up this. Typically around 10 minutes is taken to do all this. and
during that time my machine virtually becomes unresponsive. I have a
P-IV as a debugger with 256 megs and windows 2kSP4.
–
- Developer
Developer wrote:
hi all,
I am using windbg version 6.4. I connect to COM2 of the machine at 19200 bauds.
I observe that initially when it hits a break point the debugger is
very slow. It takes ages to load the symbols and then another
millenium to execute the first command I type, is there a way to sped
up this. Typically around 10 minutes is taken to do all this. and
during that time my machine virtually becomes unresponsive. I have a
P-IV as a debugger with 256 megs and windows 2kSP4.
Two suggestions: connect at 115200 or 230400 baud, or use a Firewire
connection.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Running WinDbg at anything less than 115200 Kbps says you have a tiny
bladder and need to visit the toilet often, or you drink lots of liquid and
need to vist the toilet, or you like to fool your boss into thinking your
working and really not goofing off. Now, at my age, the visit to the toilet
is a good excuse.
Seriously … jack the bps up. If you can go to 1394, do so, but that in and
of itself is a bit tricky requiring a TI chipset in the 1394 hardware.
–
The personal opinion of
Gary G. Little
“Developer” wrote in message news:xxxxx@windbg…
hi all,
I am using windbg version 6.4. I connect to COM2 of the machine at 19200
bauds.
I observe that initially when it hits a break point the debugger is
very slow. It takes ages to load the symbols and then another
millenium to execute the first command I type, is there a way to sped
up this. Typically around 10 minutes is taken to do all this. and
during that time my machine virtually becomes unresponsive. I have a
P-IV as a debugger with 256 megs and windows 2kSP4.
–
- Developer
Why Doesn’t WinDbg 6.4 support more that 115200 bauds. In the documentation
it is written so.
Tim suggested I use 230400
Two suggestions: connect at 115200 or 230400 baud, or use a Firewire
connection.
I read up about com baud rates, * 31250 is also available.
Developer
*
On 8/27/05, Gary G. Little wrote:
>
> Running WinDbg at anything less than 115200 Kbps says you have a tiny
> bladder and need to visit the toilet often, or you drink lots of liquid
> and
> need to vist the toilet, or you like to fool your boss into thinking your
> working and really not goofing off. Now, at my age, the visit to the
> toilet
> is a good excuse.
>
> Seriously … jack the bps up. If you can go to 1394, do so, but that in
> and
> of itself is a bit tricky requiring a TI chipset in the 1394 hardware.
>
> –
> The personal opinion of
> Gary G. Little
>
> “Developer” wrote in message news:xxxxx@windbg…
> hi all,
>
> I am using windbg version 6.4. I connect to COM2 of the machine at 19200
> bauds.
>
> I observe that initially when it hits a break point the debugger is
> very slow. It takes ages to load the symbols and then another
> millenium to execute the first command I type, is there a way to sped
> up this. Typically around 10 minutes is taken to do all this. and
> during that time my machine virtually becomes unresponsive. I have a
> P-IV as a debugger with 256 megs and windows 2kSP4.
>
>
> –
>
> - Developer
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@gmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
–
- Developer
Because there is not a single standard for chips supporting greater than
115200. There are boards that have multiplier options, i.e. you specify
115200 and you get 230400 or even 460800.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Developer” wrote in message news:xxxxx@windbg…
Why Doesn’t WinDbg 6.4 support more that 115200 bauds. In the documentation
it is written so.
Tim suggested I use 230400
>Two suggestions: connect at 115200 or 230400 baud, or use a Firewire
>connection.
I read up about com baud rates, * 31250 is also available.
Developer
*
On 8/27/05, Gary G. Little wrote:
>
> Running WinDbg at anything less than 115200 Kbps says you have a tiny
> bladder and need to visit the toilet often, or you drink lots of liquid
> and
> need to vist the toilet, or you like to fool your boss into thinking your
> working and really not goofing off. Now, at my age, the visit to the
> toilet
> is a good excuse.
>
> Seriously … jack the bps up. If you can go to 1394, do so, but that in
> and
> of itself is a bit tricky requiring a TI chipset in the 1394 hardware.
>
> –
> The personal opinion of
> Gary G. Little
>
> “Developer” wrote in message news:xxxxx@windbg…
> hi all,
>
> I am using windbg version 6.4. I connect to COM2 of the machine at 19200
> bauds.
>
> I observe that initially when it hits a break point the debugger is
> very slow. It takes ages to load the symbols and then another
> millenium to execute the first command I type, is there a way to sped
> up this. Typically around 10 minutes is taken to do all this. and
> during that time my machine virtually becomes unresponsive. I have a
> P-IV as a debugger with 256 megs and windows 2kSP4.
>
>
> –
>
> - Developer
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@gmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
–
- Developer