topic crash when initializing xmTextFieldWidgetClass in Operating System - HP-UX

crash when initializing xmTextFieldWidgetClass

Bart Vanneste — Thu, 31 Jul 2003 13:49:39 GMT

Hello,

I've a crash when trying to the xmTextFieldWidgetClass on HP-UX 11.11
Motif2.1 is used and X11R6.
Attached is a little program that reproduces the problem. Also the 'call stack' when crashed is included.
I've already installed patch PHSS_28371 but it had no effect.
When I compile on HP-UX 10.20 there is no problem (Motif1.2 / X11R6)

Any ideas on what might cause this and/or
ways to fix it?

Re: crash when initializing xmTextFieldWidgetClass

Steven E. Protter — Thu, 31 Jul 2003 14:00:52 GMT

Does the crash create a core dump or a crash dump in /var/adm/crash

If it really crashes the machine, perform q4 analysis on it. Instructions attached.

SEP

Re: crash when initializing xmTextFieldWidgetClass

Bart Vanneste — Thu, 31 Jul 2003 14:15:21 GMT

It's only the program that crashes.
No core is dumped.
It says "Bus error" when exiting.

Re: crash when initializing xmTextFieldWidgetClass

Mike Stroyan — Mon, 04 Aug 2003 18:55:24 GMT

This answer is a repeat of my response to you in the dev-tools mailing list. I'll put it here for the benefit of other folks trying to answer the question now and for future searches of the same topic.
---------------------------------------------------------------------------
The Motif2.1 code assumes that the vendorShellWidgetClass has been
initialized before other Motif widget classes. The XtAppInitialize
version of your test works because it creates an ApplicationShell
widget, which initializes the applicationShellWidgetClass and its
superclass, the vendorShellWidgetClass. That calls several functions
to set up global data. The vital function in this case was
_XmInitializeTraits, which initializes a global pointer
used code under by XtInitializeWidgetClass(xmTextFieldWidgetClass).

It is not clear if the Motif2.1 authors were right to assume that
vendorShellWidgetClass would be initialized first. But that is
the way it is. You can work around it with the following call.

#include
XtInitializeWidgetClass(vendorShellWidgetClass);