You need to supply some information about the input. Most likely the cause is attempting to display a very large number of samples.
However, it's also possible that your per process limits are set too low. What does "ulimit -a" return? There's really no reason to set the data, stack & vmemory limits to anything less than unlimited. Back it the days of the VAX 11/780 it made sense, but not when a typical machine has gobs of disk space and physical memory and is only used by one person.
I have 4 GB of DRAM and 32 GB of swap space. I don't normally ever start paging, but if I want to have 20-30 large seismic plots iconified so I can call them up quickly, the extra swap space lets me do that.
Have Fun!
Reg
--- On Thu, 8/7/08, Nadia Kreimer <nadi...@hotmail.com> wrote:
> From: Nadia Kreimer <nadi...@hotmail.com>
> Subject: [CWP/SU] malloc failed
> To: seis...@dix.mines.edu
> Date: Thursday, August 7, 2008, 7:20 AM
> Hello,
> I'm using a unix script in Seismic Unix that creates a
> spike and then applies a filter, and plots the results. I
> keep having an error that I don't know how to handle. It
> says:
> "/usr/local/cwp/bin/ximage: ealloc.c: malloc failed
> (Cannot allocate memory)"
>
> I'm running SU in an Ubuntu Hardy version, in a Compaq
> Presario. I tried modifying the ColorDepth, but the problem
> doesn't vanish. I'll appreciate some advice...
> Thank you all!
>
> Nadia
>
>
> _________________________________________________________________
> Descargá GRATIS el poder del nuevo Internet Explorer 7.
> http://optimized.msn.com/Default.aspx?mkt=es-ar_______________________________________________
> seisunix mailing list
> seis...@dix.mines.edu
> http://www.cwp.mines.edu/mailman/listinfo/seisunix
_______________________________________________
seisunix mailing list
seis...@dix.mines.edu
http://www.cwp.mines.edu/mailman/listinfo/seisunix
It's a bug in ximage.c. You're specifying hbox & wbox incorrectly which is what triggered the bug. These should be integer values for the number of pixels, e.g. wbox=400 hbox=600. However, ximage should not calculate a negative width in xSizeAxesBox() which will then cause malloc to fail.
Have Fun!
Reg
-John
> _________________________________________________________________
> Ingresá ya a MSN Deportes y enterate de las últimas novedades del mundo deportivo.
> http://msn.foxsports.com/fslasc/
John Stockwell | jo...@dix.Mines.EDU
Center for Wave Phenomena (The Home of Seismic Un*x)
Colorado School of Mines
Golden, CO 80401 | http://www.cwp.mines.edu/cwpcodes
voice: (303) 273-3049
Our book:
Norman Bleistein, Jack K. Cohen, John W. Stockwell Jr., [2001],
Mathematics of multidimensional seismic imaging, migration, and inversion,
(Interdisciplinary Applied Mathematics, V. 13.), Springer-Verlag, New York.
Check your wbox and hbox parameters. They are quite small, which could be causing your problem. Try running with the default values of wbox and hbox, and the malloc failure should disappear.
Brian
-John