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 > > >On Mon, 2003-06-23 at 17:55, David Thompson wrote: > >> Start up, load /usr/local/dx/samples/programs/AutoColor.net, quit. > >> > >> That's enough to see it happen. For me. > >> > >> David > >> > >...still looking. > > > >I see the XtError message at exit that you mentioned but only > >if I execute AutoColor.net. Loading and quiting doesn't do it > >for me. > > > >As I mentioned before, I recall seeing this error message but > >that it went away (somehow). Now I observe that my build > >with source unchanged but with a few files built with > >-g (instead of -g -O2), doesn't exhibit the behavior. > > > >I have noticed that my malloc checker always complains > >about a memory problem in libXt when dxui exits that > >involves a call to XtPopdown from Motif's tool tip code. > > > >Martin > > > -- > ............................................................................. > David L. Thompson Visualization and Imagery Solutions, Inc. > mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804 > Phone : (406)756-7472
