frequent "memory has been corrupted" errors

[Guest]

On Fri, Oct 07, 2005 at 10:02:11PM -0700, Mike Fitzpatrick wrote:
>
> Hi Gabriel,
> The ulimit trick usually fixes this but only when the memory
> corrupted comes from all tasks. If this is limited to MKOBJECTS then
> it may be related to the data itself and be no more than a bug in the
> task. Does it happen reliably with your e.g. object list but not when
> trying one of the help page examples? Does it happen for any other task?
> If it is limited to the one task and your data files, could you
> please put your sample input image and object list in the /pub of our
> ftp://iraf.noao.edu archive so we can have a look? Also, it would help
> to know what distribution of Linux you're using and the IRAF version
> (i.e. V2.12.2 or the V2.12.2a patch from Jul04)? Note that there are
> some known issues with the Debian package created by one of the users,
> if you're using this try installing the binaries from our archive instead.
> Hope this helps.
>

Hi Mike,

I am running Debian (sarge) running kernel 2.6.11-1-686-smp, but not
using the Debian packages. My instance identifies itself as:

NOAO PC-IRAF Revision 2.12.2a-EXPORT Wed Jul 14 20:45:34 MST 2004
This is the EXPORT version of PC-IRAF V2.12 supporting most PC systems.

I seem to get similar errors with a much simpler task:

grosa@pookie:~$ /usr/local/iraf/irafbin/noao.bin.linux/x_ccdred.e 'mkimage image=foo.fits option=make value=0 ndim=2 dims="500 500" slope=0 sigma=0 seed=0 pixtype="real"'
free(): invalid pointer 0xb7ec502e!

PANIC in `/usr/local/iraf/irafbin/noao.bin.linux/x_ccdred.e': Memory has been corrupted

and likewise:

grosa@pookie:~$ /usr/local/iraf/irafbin/noao.bin.linux/x_artdata.e 'mknoise input=noise.fits ncols=$1 nlines=$2 backgro=100.0 poisson+ nxc=5 nyc=5 nxsub=10 nysub=10 nxgsub=1 nygsub=1 dynrange=100000 psfrange=100000 background=100 ranbuf=0 @mknoise.par'

PANIC in `/usr/local/iraf/irafbin/noao.bin.linux/x_artdata.e': Memory has been corrupted

It seems like just about anything I do causes this memory error. I'd
hazard a guess that the previous mkobject problem was not data related.

-Gabe
--
Gabriel G. Rosa | For some reason, normal sane people seem to lose all of
Programmer, Physics | their common sense when sitting in front of a computer.
512 Physics/Geology | To the point where plain messages e.g. "Please Insert a
(530) 754-8235 | Floppy", evoke a response of "What does that mean?" -AM


Post generated using Mail2Forum (http://www.mail2forum.com)