Martin,
Sorry about this. It is related to the tooltips. At one time I had it
fixed and didn't realize that the updated code didn't make it into
OpenMotif 2.2.2. It is actually post 2.2.2. You can see the fix that
Rick Scott and myself discovered at
<http://cvs.motifzone.net/cgi-bin/cvsweb.cgi/openmotif/lib/Xm/ToolTip.c.diff?r1=1.3&r2=1.4&cvsroot=openmotif>.
It does require a recompile of OpenMotif in my case of the crash. For
the other systems, I'll live with the error message.
David
On Tue, 2003-06-24 at 11:17, David Thompson wrote:
Which version of Motif are you using. There was a problem I found in
OpenMotif's tool tip code that I got them to fix, but I think in
order for it to be fixed you need 2.2.2.
From Xm/Xm.h:
My XmVERSION_STRING says 2.2.2. My XmUPDATE_LEVEL says 3.
That is not the problem I see.
As you note, I did have to execute to make it appear. I guess I
always load, execute, quit, to do tests--force of habit.
On MacOS X, I can't build with -O2 because of some problems with
their optimizing routines that cause other problems--none the less,
have you discovered a fix for what I see--or are you saying that it
isn't an error?
I didn't mean to suggest that the problem originated in the compiler's
optimizer. I was just saying that unrelated mods to
the organization of the .o file have the effect of
changing the way the bug behaves. ...which might happen if the bug
were a memory problem like the kind you would track down using
purify.
Actually, do we know that there is only 1 bug? I mean, if you were
to double check a stack trace from the crash you're getting, are
you sure it's going through TextSelector.C? If so, then it's
something different from what I'm looking at. If you are really just
starting up, loading AutoColor.net, executing once, then quitting,
and you're getting a crash that goes through TextSelector.C, then
something is really screwed up.
I installed an Xt error handler so that I could break in the handler
and know for sure who was the dirty bird calling XtPopdown
incorrectly. I found that when I did
this, there was no longer an error being issued. Then I found
that if I simply returned to the code to its original state, there
was also no error. So I had 2 copies of dxui - 1 built normally
and one built with a few files with -g - and they behaved
differently with respect to this bug.
--
.............................................................................
David L. Thompson Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804
Phone : (406)756-7472
