‘Segmentation violation’ while doing ‘zerocombine’ in Suse
Hualee Lee wrote on Aug 08, 2007
System : Suse 10
Iraf vertion : V2.12
PACKAGE = ccdred
TASK = zerocombine
Such information appeared :
ERROR on line 46 : segmentation violation
zerocombine (mode=h)
What's wrong?
Thanks!
Iraf vertion : V2.12
PACKAGE = ccdred
TASK = zerocombine
Such information appeared :
ERROR on line 46 : segmentation violation
zerocombine (mode=h)
What's wrong?
Thanks!
Mike Fitzpatrick wrote on Aug 08, 2007
There's not a lot of information to go on, but I have two guesses:
Suse 10 uses the Linux 2.6 kernel and *if* you get a similar segfault from any task then you may be seeing a "stacksize" error caused by a change in the memory management under 2.6. This is fixed by issuing either of the commands:
I'd suggest putting these in your .cshrc file if you don't type them in the commandline before logging in. Note the 'cl' command is a C-shell script and so to make this permanent you'll need to put it in a .cshrc file regardless of what shell you use.
The second guess has to do with the mixed use of image types, e.g. your input images are FITS but your imtype is 'imh' and there is some problem with creating imh temp images on your system (e.g. an invalid 'imdir' , permission problems in the directory, etc). In this case doing a
usually helps since it forces the temp images to be done as FITS as well. You can make this change permanent by editing your login.cl file.
Otherwise we'd need more information such as sample data and the parameters you used. Hope this helps.
Cheers,
-Mike
Suse 10 uses the Linux 2.6 kernel and *if* you get a similar segfault from any task then you may be seeing a "stacksize" error caused by a change in the memory management under 2.6. This is fixed by issuing either of the commands:
% limit stacksize unlimited # for C-shell
% ulimit -s unlimited # for BashI'd suggest putting these in your .cshrc file if you don't type them in the commandline before logging in. Note the 'cl' command is a C-shell script and so to make this permanent you'll need to put it in a .cshrc file regardless of what shell you use.
The second guess has to do with the mixed use of image types, e.g. your input images are FITS but your imtype is 'imh' and there is some problem with creating imh temp images on your system (e.g. an invalid 'imdir' , permission problems in the directory, etc). In this case doing a
cl> reset imtype = fits
cl> flpr 0 # zero not oh
usually helps since it forces the temp images to be done as FITS as well. You can make this change permanent by editing your login.cl file.
Otherwise we'd need more information such as sample data and the parameters you used. Hope this helps.
Cheers,
-Mike
Hualee Lee wrote on Aug 08, 2007
.
---------- It's true , the path of my imh temp images is "/iraf/imdirs",
but in login.cl file it turns out to be "/iraf/imdirs/lhl".
It works with making them the same.
Thanks Mike!
~Myla
.. 'there is some problem with creating imh temp images on your system (e.g. an invalid 'imdir' )'
---------- It's true , the path of my imh temp images is "/iraf/imdirs",
but in login.cl file it turns out to be "/iraf/imdirs/lhl".
It works with making them the same.
Thanks Mike!
~Myla
Last post on Aug 08, 2007