Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!unmvax!ncar!boulder!stan!toml
From: toml@Solbourne.COM (Tom LaStrange)
Newsgroups: comp.windows.x
Subject: Re: debugging window managers
Message-ID: <1309@imelda.Solbourne.COM>
Date: 1 Jun 89 14:09:45 GMT
References: <1979@husc6.harvard.edu>
Distribution: usa
Organization: Solbourne Computer Inc., Longmont, Co.
Lines: 26

From article <1979@husc6.harvard.edu>, by kochhar@endor.harvard.edu (Sandeep Kochhar):
> (While the following problem occurred when I was debugging some
> changes I tried to make to twm, I think the problem might be
> more general -- basically, debugging any window manager)
> 
> 
> I made some changes to twm and tried debugging using both
> "dbx" and "saber" and ran into the following problem: basically,
> either twm would hang in "select.o" or would hang the server.
> 
> Do I need to do something special to use dbx or saber with twm
> or should it have worked fine (like any other program)?
> 
> Thanks for any help.

twm will grab the server during operations that should not be interrupted.
If you are debugging the window manager on the same screen that you are
running on and you happen to hit a break point in code where the server
is grabbed, you're out of luck.  I use a terminal running dbx, but I
certainly wouldn't mind having another workstation on my desk. :-)

--
Tom LaStrange

Solbourne Computer Inc.    ARPA: toml@Solbourne.COM
Longmont, CO               UUCP: ...!{boulder,nbires,sun}!stan!toml