Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!ncar!ico!auto-trol!marbru
From: marbru@.auto-trol.com (Martin Brunecky)
Newsgroups: comp.windows.x
Subject: XtAppWarningMsg in Shell.c (X11R4)
Keywords: Xt
Message-ID: <1991May3.171416.11679@auto-trol.com>
Date: 3 May 91 17:14:16 GMT
Sender: news@auto-trol.com
Organization: Auto-trol Technology Corporation
Lines: 34
Originator: marbru@attc
Nntp-Posting-Host: server_1-gw

The Xt specification describes the high level error nad warning handler
procedure as:

typedef void (*XtErrorMsgHandler)(name, type, class, defaultp, pars, num_params)
.....
String *params;
Cardinal *num_params;


The Shell.c (and who knows how many more locations in Xt) invoke this handler
with:

               XtAppErrorMsg(XtWidgetToApplicationContext(wid),
                        "invalidWindow","eventHandler",XtCXtToolkitError,
                        "Event with wrong window",
                        (String *)NULL, (Cardinal *)NULL);
                                                    ^^^^^

Contrary to the default Xt error/warning handlers, MY code tries to USE
the num_params argument:

    n = *num_params;

When called from the Shell (and similar places), my code bombs. Is this
a documented / expected behavior ????
(I sure can check for a NULL pointer - but in how meny more places ???)



-- 
=*= Opinions presented here are solely of my own and not those of Auto-trol =*=
Martin Brunecky                      marbru%auto-trol@sunpeaks.central.sun.com
(303) 252-2499                       (better avoid:  marbru@auto-trol.COM )
Auto-trol Technology Corp. 12500 North Washington St., Denver, CO 80241-2404