Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!exodus!dmaustin From: dmaustin@vivid.sun.com (Darren Austin) Newsgroups: comp.windows.x Subject: Re: dbxtool and xview programs Message-ID: Date: 8 Feb 91 23:36:39 GMT References: <4619@melon11.UUCP> <30451@shamash.cdc.com> Sender: news@exodus.Eng.Sun.COM Followup-To: comp.windows.x Organization: Sun Microsystems, Mountain View Lines: 30 In-reply-to: deano@raistlin.uucp's message of 8 Feb 91 20:47:29 GMT In article <30451@shamash.cdc.com> deano@raistlin.uucp (dean mason - 535-4717) writes: 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? Try running the program inside dbxtool with "run -Wfsdb" (full screen debug). This will shut off attempts by the XView library to grab the server, which I believe is the problem you are running into. You might want to take a look at the man page on xview (1) for more information on the debugging options available to you from the command line. Hope this helps, --Darren -- Darren Austin | Actually, it's a buck and a quarter Windows and Graphics Software | staff, but I'm not going to tell Sun Microsystems, Mountain View | *him* that. dmaustin@sun.com |