Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!sun-barr!newstop!jethro!looney.Corp.Sun.COM!toone
From: toone@looney.Corp.Sun.COM (Nolan C. Toone)
Newsgroups: comp.windows.x
Subject: Re: dbxtool and xview programs
Keywords: ARGGHHH!!!!!
Message-ID: <3385@jethro.Corp.Sun.COM>
Date: 9 Feb 91 20:35:30 GMT
References: <4619@melon11.UUCP> <FISCHER.91Feb7210311@thiele.iesd.auc.dk> <30451@shamash.cdc.com>
Sender: news@jethro.Corp.Sun.COM
Organization: Sun Microsystems, Mt. View, Ca.
Lines: 29

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.
>
>The problem is that when I set a breakpoint inside one of
>my callbacks, it stops all right, the whole damn window manager
>locks up!
>
>How are we supposed to debug  xview applications without a debugger?
>

My opinion of what is happening:
the callbacks are grabbing the screen and waiting for specific 
input from the notifier. the dbx (as part of the windows) has
the process stoped. no input to the process because dbx has it stopped
and no input to dbx be cause the process has the focus.

Temporary solution:
Use /bin/dbxtool. This is the sunview dbxtool that runs under
sunview compatability mode. Sunview goes directly to/from the
system bypassing the window manager etc. so **IT** won't hang.
(Every thing else will but as soon as you exit dbxtool they
all return).

Long term solution:
Hope a solution comes out before sunview dbxtool disappears.

Nolan Toone