Path: utzoo!bnr-vpa!bnr-fos!bigsur!darren2
From: darren2@bigsur.UUCP (Darren Toop)
Newsgroups: comp.windows.x
Subject: Re: Debugging while server grabs are present.
Message-ID: <427@bigsur.UUCP>
Date: 22 Oct 89 01:34:31 GMT
Reply-To: darren2@bigsur.UUCP (Darren Toop)
Organization: Bell-Northern Research, Ottawa, Canada
Lines: 29

This is a fairly well known problem to me, since I do alot of dbx
of x applications.  I also use Saber-C debugger and it has the same 
problem.  I use a brute force work around as follows:

You may not be able to type, but you can still cut and paste.
cat the following file in scratch pad window:

s
n
c
quit
p x
p *x
dump
display
abcdefghijklmnopqrstuvwxyz
ABCDEFGHIJKLMNOPQRSTUVWXYZ
!@#$%^&*()-_=+\|`~[{}];:'",<.>/?  

Then when I get stuck, I can still cut+paste the command I want
into the dbx input buffer and it will do the command.  Hey, nobody
said it was elegant.  If you've got a better way, let me know.

With Saber-C the problems are a bit more nasty, since, if you
mistype a command sometimes Saber will echo it back on the command
line.  This is great if you can use the keyboard, but it's hard to
paste a backspace character.  :-)  (Anybody from Saber listening out there.)

regrads .. Darren Toop