Xref: utzoo comp.windows.x:32512 comp.windows.open-look:557
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!src.honeywell.com!msi.umn.edu!cs.umn.edu!uc!shamash!raistlin!deano
From: deano@raistlin.uucp (dean mason - 535-4717)
Newsgroups: comp.windows.x,comp.windows.open-look
Subject: dbxtool and xview programs
Keywords: ARGGHHH!!!!!
Message-ID: <30451@shamash.cdc.com>
Date: 8 Feb 91 20:47:29 GMT
References: <4619@melon11.UUCP> <FISCHER.91Feb7210311@thiele.iesd.auc.dk>
Sender: usenet@shamash.cdc.com
Reply-To: deano@raistlin.udev.cdc.com
Followup-To: comp.windows.x
Organization: Aggregate Computing, Inc.
Lines: 17


Has anyone had the pleasure of trying to debug an xview program
with dbxtool.  Maybe it is just my setup but I am running an
IPC with fullup SunOS 4.1.1 straight off the tape.  

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!  I suspect (hopefully incorrectly) that this is due to
the implementation of event handling through a central "notifier"
and that the notifier is perhaps "hung" waiting on the event I trapped
to finish?  Is this the problem?  Any work arounds?  I haven't tried
it with straight dbx, but I've seen the exact same thing with adb.

How are we supposed to debug  xview applications without a debugger?


deano@raistlin.udev.cdc.com