iraf.net

Hi IRAF gurus,
I hope all is well.We are running some initial tests with RedHat Enterprise Linux 3
Update 1 and IRAF 2.12.1. Today we saw this error for the first time:> PANIC in `/usr/local/iraf/iraf/bin.redhat/x_images.e': Memory has been
> corruptedI see your reference to this happening with Fedora on the v2.12.2
beta 2 web page: http://iraf.noao.edu/iraf/web/new_stuff/v2122-beta2.htmlBut the solution there is not helpful on RHEL, as it does not
have an "exec-shield" kernel setting.Do you have any other ideas as to what might cause this error?Thanks very much,
Patrick*---------------------------------------------------------------------*
| Patrick Shopbell Department of Astronomy |
| pls@astro.caltech.edu Mail Code 105-24 |
| (626) 395-4097 California Institute of Technology |
| (626) 568-9352 (FAX) Pasadena, CA 91125 |
| WWW: http://www.astro.caltech.edu/~pls/ |
*---------------------------------------------------------------------*

Hi Patrick,
You didn't say exactly which task you were running so it's hard to
tell if it's a system problem or just a known bug. However, you're only
the second user to report using RHEL 3 and the second to have problems.
First, is this the 'stock' V2.12.1 or the Redhat 9 compatability
release? Do problems appear in other tasks (the other user is having fits
with HELP for instance)? Does it make a difference if you use FITS or
.imh images? We're about to release the final V2.12.2 system with Fedora
support but (more or less) the final distribution files are in the
ftp://iraf.noao.edu/pub/V2.12.2-BETA/PCIX directory if you'd like to see
whether it makes a difference. If every task has a similar problem I'd
suspect it was some kind of system incompatability, if it's just this one
it may already be something fixed in the new release.
We don't yet have any first-hand experience with RHEL so I can't
be more specific. If you'd like us to (let us) poke around your system
in case this doesn't turn up anything simple let me know.Cheers,
-Mike

On Tue, 3 Feb 2004 17:04:50 -0800
Patrick Shopbell <pls@astro.caltech.edu> wrote:>
> Hi IRAF gurus,
> I hope all is well.
>
> We are running some initial tests with RedHat Enterprise Linux 3
> Update 1 and IRAF 2.12.1. Today we saw this error for the first time:
>
> > PANIC in `/usr/local/iraf/iraf/bin.redhat/x_images.e': Memory has
> > been corrupted
>
> I see your reference to this happening with Fedora on the v2.12.2
> beta 2 web page:
>
> http://iraf.noao.edu/iraf/web/new_stuff/v2122-beta2.html
>
> But the solution there is not helpful on RHEL, as it does not
> have an "exec-shield" kernel setting.
>
> Do you have any other ideas as to what might cause this error?
>
> Thanks very much,
> PatrickHi Patrick,You are the second person to report an issue with IRAF on Enterprise 3.
Unfortunately we have not found a solution yet, as we need more info.Could you also provide the checksum for x_image.e, i.e.,
"sum /usr/local/iraf/iraf/bin.redhat/x_image.e"?Do you notice this error with other tasks, e.g., help?Could you please specify which version of glibc is on your system, i.e.,
"rpm -qa | grep glibc"?Regards,Phillip

Hi Patrick,It seems that we (Mike Fitzpatrick, actually) have found a workaround
for the memory corruption messages you were seeing.Basically, this is the same problem that we were seeing on Fedora, where
disabling exec-shielding would fix this. However, as you know,
exec-shielding is not included in RHE3.The workaround is simple: You should add the following line to your .cshrc file (or cl.csh in
$iraf/unix/hlib/): limit stacksize unlimitedYou may wish to install the soon-to-be-released V2.12.2, as this
addresses many other bugs and issues. Hopefully the release will be
within the next few days or so.I hope that helps. Let us know if you have further questions or
problems.Cheers,Phillip

Hi Phillip,On Wed, Feb 04, 2004 at 11:12:42PM -0700, Phillip Warner wrote:
>
> It seems that we (Mike Fitzpatrick, actually) have found a workaround
> for the memory corruption messages you were seeing.
>
> Basically, this is the same problem that we were seeing on Fedora, where
> disabling exec-shielding would fix this. However, as you know,
> exec-shielding is not included in RHE3.
>
> The workaround is simple:
>
> You should add the following line to your .cshrc file (or cl.csh in
> $iraf/unix/hlib/):
>
> limit stacksize unlimitedThis is excellent news! We will try this in the next day or so
and let you know if it works for us.Thanks very much.
--
Patrick*--------------------------------------------------------------------------*
| Patrick Shopbell Department of Astronomy |
| pls@astro.caltech.edu Mail Code 105-24 |
| (626) 395-4097 California Institute of Technology |
| (626) 568-9352 (FAX) Pasadena, CA 91125 |
| WWW: http://www.astro.caltech.edu/~pls/ |
*--------------------------------------------------------------------------*