iraf.net

I'm trying to use ncl (SAO's "new" cl, which has command-line editing) with Fedora Core 5 and IRAF 2.12.2a-EXPORT.When I run it I get PANIC "memory has been corrupted problems" when doing things like "imstat dev$pix".I've tried recompiling ncl from the source (which incidentally required setting the XC_CC and XC_LINKER environment variables to gcc32, since the IRAF cl doesn't compile with version 4 gcc due to problems with varargs), but this hasn't helped.Any ideas?Cheers,
Michael Ashley / University of New South Wales

Hi Michael,[quote:0f0a4dd3dc]
I'm trying to use ncl (SAO's "new" cl, which has command-line editing) with Fedora Core 5 and IRAF 2.12.2a-EXPORT.[/quote:0f0a4dd3dc]Note, the ECL (Enhanced CL) has the same cmdline editing capability as well as error handling. It is the standard CL for the V2.13-beta2 release from this site or as an add-on for earlier releases. I don't think NCL is still being supported, but that isn't part of the problem anyway.[quote:0f0a4dd3dc]
When I run it I get PANIC "memory has been corrupted problems" when doing things like "imstat dev$pix".[/quote:0f0a4dd3dc]Sounds like the 'stacksize problem' in V2.6 kernels. It could mean the iraf installation was updated with a source patch but the binaries are from an earlier version, check that they date from July '04 (i.e. "cl> dir bin$*.e long+"). The fix is to issue the commandlimit stacksize unlimited (for c-shell users, or)
ulimit -s unlimited (for bash users) The 'cl' command script should do this automatically, verify that hlib$cl.csh has the above 'limit' command in it. Otherwise, issue the command at the unix prompt before typing 'cl' and let me know if you still have problem.[quote:0f0a4dd3dc]
I've tried recompiling ncl from the source (which incidentally required setting the XC_CC and XC_LINKER environment variables to gcc32, since the IRAF cl doesn't compile with version 4 gcc due to problems with varargs), but this hasn't helped. [/quote:0f0a4dd3dc]Just FYI, the various gcc 4/varargs problems in the system are fixed in the V2.13 series. Hope this helps.Cheers,
-Mike

Hi Mike,Thanks for your rapid and accurate reply.[quote:84471bb7b7="fitz"]
Sounds like the 'stacksize problem' in V2.6 kernels. It could mean the iraf installation was updated with a source patch but the binaries are from an earlier version, check that they date from July '04 (i.e. "cl> dir bin$*.e long+"). The fix is to issue the commandlimit stacksize unlimited (for c-shell users, or)
ulimit -s unlimited (for bash users) [/quote:84471bb7b7]Yep, that was it! I do have July '04 binaries, but the ncl script wasn't unlimiting the stack. Thanks for the pointer to ECL.Cheers,
Michael