iraf.net

Hi Ana,
As I've said, we can't do much to support other distributions you
might find on the net and there are some known/reported problems with the
Debian package. One thing you might try is to issue the command limit stacksize unlimited # for csh
ulimit -s unlimited # for basheither in your .cshrc/.bashrc or on the commandline before logging in.
This fixes a problem with some linux 2.6 kernels but I'm only guessing
is the cause of your problem. If that doesn't work, you'll need to
either install the distribution from our archives or contact the
debian package author to see if he's aware of problems.Cheers,
-MikeOn Sat, 19 Nov 2005, ana nicuesa wrote:> Hi Mike, how are you?
> Sorry for bothering you again. I didn't follow your
> rules. I installed an iraf I found on the internet , I
> think you can understand a little spanish.
> Instalado automáticamente: no
> Versión: 2.12.2a-10
> Prioridad: extra
> Sección: science
> Desarrollador: Justin Pryzby
> <justinpryzby@users.sf.net>
> Tamaño sin comprimir: 71,2M
> Depende de: libc6 (>= 2.3.2.ds1-4), debconf (>= 0.5) |
> debconf-2.0, tcsh |
> c-shell, f2c, debconf (>= 0.5)
> Recomienda: iraf-common, iraf-doc
> Tiene conflictos con: xpp
> THE MOST IMPORTANT THING IS THAT HAVE PROBLEMS XPP ( I
> HAVE NO IDEA WHAT DOES IT MEAN). ANOTHER PROBLEM IS
> THAT IF I TRY TO PLOT WITH IMPLOT IRAF SAIS
> pl> implot
> image to be plotted ( 0061030071.fits ):
>
> PANIC in `/usr/lib/iraf/iraf//bin/x_plot.e': Memory
> has been corrupted
> pl>
> DO YOU KNOW HOW TO SOLVE?YOU ARE LIKE A DOCTOR, I JUST
> SHOW YOU WHAT'S GOING ON ...AND MAYBE YOU CAN GIVE ME
> A RECIPE.
> MAYBE I HAVE TO FOLLOW YOUR FIRST INSTRUCTION, INSTAL
> THE BINARIES... BUT I THINK THIS IS QUITE DIFICULT.
> ANYWAY THANK YOU FOR YOUR HELP.
> CHEERS.
> ANA
>
>
>
>
> ______________________________________________
> Renovamos el Correo Yahoo!
> Nuevos servicios, más seguridad
> http://correo.yahoo.es
>

1) The conflict with xpp is only a problem if you want to install a package named xpp on the same system (regardless of what it does).2) Whenever I've seen the "Memory has been corrupted" message it was indeed enough to raise the stack size limit (I haven't tried to see if large but finite values also work).
Note that (a) Justin Pryzby is well aware of the problem, and (b) the workaround is built into the cl.csh script in the NOAO distribution of IRAF.The workaround is *not* built into PyRAF yet (as of PyRAF 1.2 / STScI Python 2.2) so you'll need it if you use PyRAF.
(By the way, I've got Debian/Ubuntu packages for STScI Python; will see about publishing them.)Sergio Gelato