FITSUTIL task gives segmentation fault
David Rupke wrote on Feb 02, 2011
Hello,
I have installed the new 2.15.1 release, which solved some other issues I was having with the initial 2.15 release. However, it has not solved a "segmentation fault" I keep getting when I try to run FXHEADER on the following image:
http://dl.dropbox.com/u/9601016/mrk231rb3.fits [30 Mb]
This was not a problem with v2.14 of IRAF, and I am at a loss.
I am running IRAF 2.15.1 on Mac OS 10.6, with the external packages installed using the new methods.
Thanks,
Dave Rupke
I have installed the new 2.15.1 release, which solved some other issues I was having with the initial 2.15 release. However, it has not solved a "segmentation fault" I keep getting when I try to run FXHEADER on the following image:
http://dl.dropbox.com/u/9601016/mrk231rb3.fits [30 Mb]
This was not a problem with v2.14 of IRAF, and I am at a loss.
I am running IRAF 2.15.1 on Mac OS 10.6, with the external packages installed using the new methods.
Thanks,
Dave Rupke
Mike Fitzpatrick wrote on Feb 02, 2011
I can reproduce the problem on 32-bit maosx systems, it appears to be a side-effect of cross-compiling on a 64-bit system. I'll post a solution shortly.
Mike Fitzpatrick wrote on Feb 02, 2011
Dave,
First, thanks for the report. From what I've been able to tell, some binaries for the 'macosx' architecture were built using the 64-bit compiler tools, meaning that some macros to dereference pointers were wrong in the final compiled code. This probably happened when I set the environment manually rather than by sourcing an env file.
Since there is no reliable way to determine which binaries might have this problem, and since you say it happened with the original v2.15 as well, I rebuilt all of the macosx binaries for the core system and external packages just to be sure.
To fix the external packages, simply go to the $iraf/extern directory and do a "make update" and you'll update all installed packages. If you notice similar problems in core system tasks, download and reapply the patch1.macx.uni.gz file by untarring in the iraf root directory with a command such as:
Again, this ONLY applies to the 'macosx' architecture. If you still hav e problems or notice other issues, please let me know.
Cheers,
-Mike
First, thanks for the report. From what I've been able to tell, some binaries for the 'macosx' architecture were built using the 64-bit compiler tools, meaning that some macros to dereference pointers were wrong in the final compiled code. This probably happened when I set the environment manually rather than by sourcing an env file.
Since there is no reliable way to determine which binaries might have this problem, and since you say it happened with the original v2.15 as well, I rebuilt all of the macosx binaries for the core system and external packages just to be sure.
To fix the external packages, simply go to the $iraf/extern directory and do a "make update" and you'll update all installed packages. If you notice similar problems in core system tasks, download and reapply the patch1.macx.uni.gz file by untarring in the iraf root directory with a command such as:
cd $iraf ; tar zxf /path/patch1.macx.uni.gzAgain, this ONLY applies to the 'macosx' architecture. If you still hav e problems or notice other issues, please let me know.
Cheers,
-Mike
David Rupke wrote on Feb 02, 2011
Mike, thanks. That seems to have fixed the problem. My machine is in principle capable of 64-bit, but I haven't switched kernels yet, hence the "macosx" architecture.
Last post on Feb 02, 2011