Submitted by Anonymous on Thu, 01/03/2002 - 10:55. Developers
I have an application which is dumping core when it is linked with Motif2.1 libraries ,
but it works fine with Motif1.2 libraries. Any idea why it is happening??
first, when you say linked do you mean
you recompile all your object files and then link to the different motif libraries, when you compile you point to the corisponding motif header files? Or are you just re-linking (ld) against the different motif libraries (perhaps using a different shared library?)
if the option is number two, you could be having problems if any of your code, especialy any widgets you have created, are accessing functions which are no longer availbable in motif 2.1, or data structures which have changed.
as dbl says, put it in a debugger. Open Motif distributed the libXm_d.a library which you should link against, its the debug library.
What platform are you running on? We moved from Solaris 2.6 to Solaris 8 (which went from Motif 1.2 to 2.1) and I had problems with my application core dumping. I submitted the problem to Sun, they generated a bug report, and sent me a patch for the libXm.so.4. If you are on a Sun, I recommend linking to the old Xm library (libXm.so.3) and see if that fixes your problem. If it does, contact them and let them know.
It could be that you are doing something illegal that happened not to be caught before.
But, generally, when you get a core dump you should suck it into a debugger so that you can get a stack trace. If the trace isn`t useful, try also running the application synchronously.