Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!uunet!mcsun!ukc!harrier.ukc.ac.uk!elder.ukc.ac.uk!rlh2
From: rlh2@ukc.ac.uk (R.L.Hesketh)
Newsgroups: comp.windows.x
Subject: Re: dbxtool and xview programs
Keywords: ARGGHHH!!!!!
Message-ID: <254@elder.ukc.ac.uk>
Date: 18 Feb 91 15:27:53 GMT
References: <FISCHER.91Feb7210311@thiele.iesd.auc.dk> <30451@shamash.cdc.com> <3385@jethro.Corp.Sun.COM>
Reply-To: rlh2@ukc.ac.uk (Richard Hesketh)
Organization: Computing Lab, University of Kent at Canterbury, UK.
Lines: 19

In article <3385@jethro.Corp.Sun.COM> toone@looney.Corp.Sun.COM (Nolan C. Toone) writes:
>In article <30451@shamash.cdc.com> deano@raistlin.udev.cdc.com writes:
>>Has anyone had the pleasure of trying to debug an xview program
>>with dbxtool.

>My opinion of what is happening:
>   no input to the process because dbx has it stopped
>and no input to dbx be cause the process has the focus.

Have you tried setting the display of the xview program to a different
display that you are running dbxtool on (using -display as an argument to the
program)?  The xview program would then be displayed on this different
display allowing dbxtool to function normally even when the xview program's
process has hit a break point whilst in a server grab etc.   It also makes
debugging actions such as rubber-banding and other pointer grab techniques
a breeze (you can get a friend to hold the buttons down whilst you scan
the source 8-).

Richard