On Wed, 26 Apr 2000, Greg Lehey wrote:
On Tuesday, 25 April 2000 at 9:39:10 +0100, Doug Rabson wrote:
On Tue, 25 Apr 2000, Greg Lehey wrote:
On Sunday, 23 April 2000 at 10:07:38 +0100, Doug Rabson wrote:
On Sun, 23 Apr 2000, Greg Lehey wrote:
In the last few days, my remote serial
On Tue, 25 Apr 2000, Greg Lehey wrote:
On Sunday, 23 April 2000 at 10:07:38 +0100, Doug Rabson wrote:
On Sun, 23 Apr 2000, Greg Lehey wrote:
In the last few days, my remote serial gdb has almost completely
stopped working. Previously I had (almost) no trouble at 38400 bps;
now I can
On Tuesday, 25 April 2000 at 9:39:10 +0100, Doug Rabson wrote:
On Tue, 25 Apr 2000, Greg Lehey wrote:
On Sunday, 23 April 2000 at 10:07:38 +0100, Doug Rabson wrote:
On Sun, 23 Apr 2000, Greg Lehey wrote:
In the last few days, my remote serial gdb has almost completely
stopped working.
On Wed, 26 Apr 2000, Greg Lehey wrote:
Even that didn't work for me. BTW, the fix had the side effect of
making the clock stand still. I've changed the code (spltty instead
The gdb code apparently assumes that the kernel debugger runs entirely
with interrupts disabled (as is required for
On Sunday, 23 April 2000 at 10:07:38 +0100, Doug Rabson wrote:
On Sun, 23 Apr 2000, Greg Lehey wrote:
In the last few days, my remote serial gdb has almost completely
stopped working. Previously I had (almost) no trouble at 38400 bps;
now I can barely get a response at all at 9600 bps.
In the last few days, my remote serial gdb has almost completely
stopped working. Previously I had (almost) no trouble at 38400 bps;
now I can barely get a response at all at 9600 bps. Does anybody have
an idea where this could be coming from?
Greg
--
Finger [EMAIL PROTECTED] for PGP public
On Sun, 23 Apr 2000, Greg Lehey wrote:
In the last few days, my remote serial gdb has almost completely
stopped working. Previously I had (almost) no trouble at 38400 bps;
now I can barely get a response at all at 9600 bps. Does anybody have
an idea where this could be coming from?
I
