Index:
[thread]
[date]
[subject]
[author]
From: Christoph Egger <Christoph_Egger@t-online.de>
To : Ville Hallik <Ville.Hallik@mail.ee>
Date: Wed, 14 Jul 1999 14:43:19 +0200 (MEST)
Re: hacking methods to find out bugs
On Wed, 14 Jul 1999, Ville Hallik wrote:
> On Wed, 14 Jul 1999, Christoph Egger wrote:
>
> > I have a SUSE 6.0 based system with kernel 2.2.10
> > SUSE 6.0 is based on glibc2.0. And I don't get a core dump, only when I
> > run it with gdb...
>
> Seems that coredumps are not allowed by default in Your system. If
> Your login shell is bash, then read "help ulimit".
Yes, the default login shell is bash.
-------------------------------------------------------------------
GNU bash, version 2.02.1(1)-release (i586-pc-linux-gnu)
Copyright 1998 Free Software Foundation, Inc.
-------------------------------------------------------------------
"help ulimit" give this:
-------------------------------------------------------------------
ulimit: ulimit [-SHacdflmnpstuv] [limit]
Ulimit provides control over the resources available to processes
started by the shell, on systems that allow such control. If an
option is given, it is interpreted as follows:
-S use the `soft' resource limit
-H use the `hard' resource limit
-a all current limits are reported
-c the maximum size of core files created
-d the maximum size of a process's data segment
-f the maximum size of files created by the shell
-l the maximum size a process may lock into memory
-m the maximum resident set size
-n the maximum number of open file descriptors
-p the pipe buffer size
-s the maximum stack size
-t the maximum amount of cpu time in seconds
-u the maximum number of user processes
-v the size of virtual memory
If LIMIT is given, it is the new value of the specified resource.
Otherwise, the current value of the specified resource is printed.
If no option is given, then -f is assumed. Values are in 1024-byte
increments, except for -t, which is in seconds, -p, which is in
increments of 512 bytes, and -u, which is an unscaled number of
processes.
--------------------------------------------------------------------
And "ulimit -a" give this:
--------------------------------------------------------------------
core file size (blocks) 0
data seg size (kbytes) unlimited
file size (blocks) unlimited
max locked memory (kbytes) unlimited
max memory size (kbytes) unlimited
open files 1024
pipe size (512 bytes) 8
stack size (kbytes) unlimited
cpu time (seconds) unlimited
max user processes 256
virtual memory (kbytes) unlimited
--------------------------------------------------------------------
But anyway, I don't understand, what ulimit have to do with core dump...
Christoph Egger
E-Mail: Christoph_Egger@t-online.de
Index:
[thread]
[date]
[subject]
[author]