Executable got Killed

[Reuben D. Budiardja]

On Tuesday 22 February 2005 11:01, Peter Teuben wrote:
> On Tue, 22 Feb 2005, Reuben D. Budiardja wrote:
> > On Monday 21 February 2005 23:19, James McKenzie wrote:
> > > Reuben D. Budiardja wrote:
> > > > Hello,
> > > > This maybe slightly OT, but I hope someone could give me some
> > > > insight.
> > > >
> > > > I have an executable that when I tried to run it, it got killed:
> > > >
> > > > $> ./boltztrans
> > > > Killed
> > >
> > > strace is your friend.  man strace for use.

> > How do I figure out who send the SIGKILL ? FWIW, this program requires
> > rather big amount of memory, is there a limit somewhere that send the
> > SIGKILL? This is on a fresh installed FC3.
>
> i bet you have a program that declared too much memory on the stack, e.g.
> in local variables. E.g. if you have (in C/C++ lingo)
<snip>
> You can try (using the limit command in csh)
> to up the stacksize, but a better way is to either declare the variable

Increasing the stacksize limit in bash using 'ulimit -s' didn't help before. I 
am still looking at the source code (it's in Fortran, 1MB size source) to try 
to figure out which part make this happens.


RDB

-- 
Reuben D. Budiardja
Dept. Physics and Astronomy
University of Tennesse, Knoxville, TN

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GIT/M/MU/P/S d-(++) s: a-- C++(+++) UL++++ P-- L+++>++++ E- W+++ 
N+ o? K- w--- !O M- V? !PS !PE Y PGP- t+ 5 X R- tv+ 
b++>+++ DI D(+) G e++>++++ h+(*) r++ y->++++
------END GEEK CODE BLOCK------