x_onedspec.e memory corrupted error in identify
aburgasser wrote on Apr 06, 2010
Hey everyone,
I'm running IRAF on Mac OS 10.6.3 using xterm -> xgterm.
While running the "identify" task in NOAO->twod->apextract i'm getting the following fatal error:
PANIC in `/iraf/iraf/noao/bin.macintel/x_onedspec.e': Memory has been corrupted
this seizes up my xgterm completely. I've seen similar cases in the forum but no suggestions for how to resolve this. Restarting IRAF and xterm have no effect on this, nor is making a new data file that is fed into identify. Any way of clearing this out?
Thanks!
Adam
I'm running IRAF on Mac OS 10.6.3 using xterm -> xgterm.
While running the "identify" task in NOAO->twod->apextract i'm getting the following fatal error:
PANIC in `/iraf/iraf/noao/bin.macintel/x_onedspec.e': Memory has been corrupted
this seizes up my xgterm completely. I've seen similar cases in the forum but no suggestions for how to resolve this. Restarting IRAF and xterm have no effect on this, nor is making a new data file that is fed into identify. Any way of clearing this out?
Thanks!
Adam
Mike Fitzpatrick wrote on Apr 06, 2010
A 'memory corrupted' usually indicates a bug in the program, but it could be one triggered by something in the data or an unusual combination of parameters. There's not much we can do to fix it without being able to reproduce the problem locally, or other isolating the cause and finding some other workaround.
Could you provide the parameters you used (e.g. a "dpar <task>" listing for all the tasks and psets you modified) and a sample image that demonstrates the problem and upload them to the anonftp at ftp://iraf.noao.edu/pub? If we can trap the problem we'll fix it for the next release and provide you with an updated binary until then.
-Mike
Could you provide the parameters you used (e.g. a "dpar <task>" listing for all the tasks and psets you modified) and a sample image that demonstrates the problem and upload them to the anonftp at ftp://iraf.noao.edu/pub? If we can trap the problem we'll fix it for the next release and provide you with an updated binary until then.
-Mike
Last post on Apr 06, 2010