From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-23888-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 25369 invoked by alias); 11 Jan 2006 04:57:40 -0000
Received: (qmail 25362 invoked by uid 22791); 11 Jan 2006 04:57:39 -0000
X-Spam-Check-By: sourceware.org
Received: from whirlwind.netspace.net.au (HELO mail.netspace.net.au) (203.10.110.76)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 11 Jan 2006 04:57:39 +0000
Received: from [192.168.0.10] (220-253-60-77.VIC.netspace.net.au [220.253.60.77]) 	by mail.netspace.net.au (Postfix) with ESMTP id 9F76E12F7DE 	for <gdb@sources.redhat.com>; Wed, 11 Jan 2006 15:57:34 +1100 (EST)
Message-ID: <43C4903F.3010503@netspace.net.au>
Date: Wed, 11 Jan 2006 04:57:00 -0000
From: Russell Shaw <rjshaw@netspace.net.au>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.11) Gecko/20050914 Debian/1.7.11-1
MIME-Version: 1.0
Cc: gdb@sources.redhat.com
Subject: Re: Core dumps
References: <20060111014313.64887.qmail@web52011.mail.yahoo.com> <43C464D2.4000107@netspace.net.au> <uu0cbqtvb.fsf@gnu.org> <43C48C5B.2040309@netspace.net.au> <20060111044455.GB676@adacore.com>
In-Reply-To: <20060111044455.GB676@adacore.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2006-01/txt/msg00088.txt.bz2

Joel Brobecker wrote:
>>$russell@home~: ulimit
>>$unlimited
>>
>>What else can i try?
> 
> What shell do you use?

russell@home~: bash --version
GNU bash, version 3.00.16(1)-release (i486-pc-linux-gnu)
Copyright (C) 2004 Free Software Foundation, Inc.

 > I use zsh, and I have to use "ulimit -c" to
> modify the core-file size:
> 
>         %ulimit
>         unlimited
>         %ulimit -a
>         cpu time (seconds)         unlimited
>         file size (blocks)         unlimited
>         data seg size (kbytes)     unlimited
>         stack size (kbytes)        8192
>         core file size (blocks)    0
>         unlimited
>         processes                  4093
>         file descriptors           1024
>         locked-in-memory size (kb) unlimited
>         memory size (kb)           unlimited
>         file locks                 unlimited
>         %ulimit -c 2000000
>         %ulimit -a
>         cpu time (seconds)         unlimited
>         file size (blocks)         unlimited
>         data seg size (kbytes)     unlimited
>         stack size (kbytes)        8192
>         core file size (blocks)    2000000
>         unlimited
>         processes                  4093
>         file descriptors           1024
>         locked-in-memory size (kb) unlimited
>         memory size (kb)           unlimited
>         file locks                 unlimited
> 

russell@home~: ulimit -a
core file size        (blocks, -c) 0
data seg size         (kbytes, -d) unlimited
file size             (blocks, -f) unlimited
max locked memory     (kbytes, -l) unlimited
max memory size       (kbytes, -m) unlimited
open files                    (-n) 1024
pipe size          (512 bytes, -p) 8
stack size            (kbytes, -s) 8192
cpu time             (seconds, -t) unlimited
max user processes            (-u) unlimited
virtual memory        (kbytes, -v) unlimited


Well that seems to say it all;)

"man ulimit" has a useless man page. However, i just
tried "help ulimit" which shows all the options;)

The backtrace in gdb is working correctly this time.
I seemed to get core files sometimes, despite not
having set ulimit -c. Maybe gdb was doing that.