home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.windows.x.motif
- Path: sparky!uunet!paladin.american.edu!howland.reston.ans.net!wupost!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!kazoo.cis.ohio-state.edu!kshomper
- From: kshomper@kazoo.cis.ohio-state.edu (keith shomper)
- Subject: Re: Menus (and other popups) with debugging
- Message-ID: <1993Jan7.143137.22088@cis.ohio-state.edu>
- Sender: news@cis.ohio-state.edu (NETnews )
- Organization: The Ohio State University Dept. of Computer and Info. Science
- References: <1ifi1qINNouh@transfer.stratus.com>
- Date: Thu, 7 Jan 1993 14:31:37 GMT
- Lines: 21
-
- In article <1ifi1qINNouh@transfer.stratus.com> lee@deneb.sw.stratus.com (Lee Cooprider) writes:
- >
- >This feels like a FAQ, but I didn't find it in the list.
- >
- >Motif causes some popup windows to grab all events when they are active.
- >For example, the standard PulldownMenu does this.
- >
- >When one is debugging the program and it comes to a breakpoint with the
- >menu active, a deadlock occurs. The program is stopped, so the menu items
- >cannot be selected, but the program can't be resumed, because the window
- >running the debugger can't get any events.
- >
- >There must be a standard solution to this problem. What is it?
- >--
- >Lee W. Cooprider PP-ASEL/IA
- >Lee_Cooprider@vos.stratus.com Skylane N2908F "Wiley"
-
- When I've run into this problem, I debug the offending program on another
- workstation. dbx or xdbx allows you to do this easily.
-
- Keith
-