yhsieh@cadence.cadence.com (Tommy Hsieh) (10/13/90)
Hi,
I have built motif 1.1 on DECStation 3100 running Ultrix 4.0. One biggest
problem I have now is every application I wrote I got core dump. The error
message is like :
Fixed up unaligned data access for pid 10235 at pc 0x4ddbb4
:
:
I used X11R4 libraries with libXm.a to compile my applications.
Does anyone out there know how to solve this problem ? Thanks in advanve.
====================================================================
I Tommy Hsieh I Cadence Design System, Inc. I
I (408) 987-5285 I 3393 Octavius Drive I
I I Santa Clara, CA 95054-3082 I
I mail address : I
I yhsieh@cadence.com I
I ...!{versatc,apollo,ucbcad,uunet}!cadence!yhsieh I
====================================================================klee@wsl.dec.com (Ken Lee) (10/13/90)
In article <1990Oct12.204211.18569@cadence.com>, yhsieh@cadence.cadence.com (Tommy Hsieh) writes: |> I have built motif 1.1 on DECStation 3100 running Ultrix 4.0. One biggest |> problem I have now is every application I wrote I got core dump. The error |> message is like : |> Fixed up unaligned data access for pid 10235 at pc 0x4ddbb4 This error usually occurs when you recast data incorrectly, for example using a variable as a structure when it was declared as a pointer to a structure, or vice versa. You can use any standard debugger to find the point of failure. Is it in your code or in Motif? -- Ken Lee DEC Western Software Laboratory, Palo Alto, Calif. Internet: klee@wsl.dec.com uucp: uunet!decwrl!klee
kaleb@thyme.jpl.nasa.gov (Kaleb Keithley ) (10/13/90)
In article <1990Oct12.204211.18569@cadence.com> yhsieh@cadence.cadence.com (Tommy Hsieh) writes: > > I have built motif 1.1 on DECStation 3100 running Ultrix 4.0. One biggest >problem I have now is every application I wrote I got core dump. The error >message is like : > Fixed up unaligned data access for pid 10235 at pc 0x4ddbb4 Sounds like you missed the instructions in the README and portingGuide that said: (README wasn't copyrighted, I hope it's okay to publish this.) Machine Dependencies The code to support the use of compound strings, found in the file ./lib/Xm/XmString.c, has a machine dependency. The compound string contains an unaligned integer. When this code is compiled without any additional flags the integer is accessed directly. If your machine can not access an unaligned integer, you can compile with the flag -DSTRINGS_ALIGNED, and the integer is accessed as two separate bytes. You can add the flag -DSTRINGS_ALIGNED to the StandardDefines line in your imake configuration file or the Makefile in ./lib/Xm. The default imake configuration file, ./config/generic.cf, does not have the -DSTRINGS_ALIGNED flag defined. ****** Whether to use the -DSTRINGS_ALIGNED flag will depend on ****** ****** your machine, not on your operating system. For instance, a ***** ****** Vax running Ultrix does not require aligned integers, how- ****** ****** ever a DECstation 3100, which is a Risc-based machine, does ****** ****** require the flag to be defined even when it is also running ****** Ultrix. (We have added the flag to DefaultCCOptions in ./config/ultrix.cf.) Some machines do not require integers to be aligned, but will respond much slower when you try to access one that is not aligned. It may be prudent to try compiling both with and without the flag, and seeing which toolkit provides better performance on your machine. -- Kaleb Keithley Jet Propulsion Labs kaleb@thyme.jpl.nasa.gov causing trouble again.
kaleb@thyme.jpl.nasa.gov (Kaleb Keithley ) (10/13/90)
In article <1990Oct12.204211.18569@cadence.com> yhsieh@cadence.cadence.com (Tommy Hsieh) writes: > > I have built motif 1.1 on DECStation 3100 running Ultrix 4.0. One biggest >problem I have now is every application I wrote I got core dump. The error >message is like : > Fixed up unaligned data access for pid 10235 at pc 0x4ddbb4 I forgot in my previous followup to this article, I just built 1.1 on DECstation 3100 last week and everything works (mwm, uil, all the demos, inhouse clients) which is why I suspect the -DSTRINGS_ALIGNED is the culprit. -- Kaleb Keithley Jet Propulsion Labs kaleb@thyme.jpl.nasa.gov causing trouble again.