Path: utzoo!utgpu!news-server.csri.toronto.edu!orasis.vis.toronto.edu!tjhorton
Newsgroups: comp.windows.x.motif
From: tjhorton@vis.toronto.edu ("Timothy J. Horton")
Subject: Re: Motif program dies on popup menus?
Message-ID: <91Apr10.203949edt.8916@orasis.vis.toronto.edu>
Organization: Department of Computer Science, University of Toronto
References: <532@shrike.AUSTIN.LOCKHEED.COM>
Date: 11 Apr 91 00:40:14 GMT
Lines: 30

aihaug@AUSTIN.LOCKHEED.COM (Daniel A Haug) writes:
>[...] the program dies with the following X error:
>
>   Request Major code  28
>   Request Minor code  0
>   Resource ID         0x80000e
>   Error Serial        #205
>   Current Serial      #206
>
>[...]I'm also very interested in what types of debugging tools I should use
>to try to track this down myself.

Run your process with _Xdebug set to 1 (or is that _xdebug?), or make a call
to XSynchronise, so that you can trace the error to the line which causes it.

These messages can tell you a lot, by the way.  Look up the Request Major Code
in /usr/include/X11/Xproto.h (on most machines).  Code 28 is defined there:
    #define X_GrabButton 28
meaning that a call to XGrabButton caused the problem (a passive grab of a
pointer button).  That may not mean much, but it narrows down the problem
in many cases.  Look, especially, for resource id's of 0.  In this case,
however, there doesn't seem to have been a return code with the error
(one of BadAccess, BadAlloc, BadCursor, BadValue, or BadWindow), or you
forgot to include the whole error message, so I can't even guess what is wrong.

Tim
-------------------------------------------------------------------------
Timothy Horton, unix software consulting
574 Spadina Avenue, Toronto, Canada M5S 2H2
tjhorton@vis.toronto.edu   (or) utai!tjhorton