Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Russell Shaw <rjshaw@netspace.net.au>
Cc: gdb@sources.redhat.com
Subject: Re: Core dumps
Date: Wed, 11 Jan 2006 04:57:00 -0000	[thread overview]
Message-ID: <43C4903F.3010503@netspace.net.au> (raw)
In-Reply-To: <20060111044455.GB676@adacore.com>

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.


  reply	other threads:[~2006-01-11  4:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09  9:33 Russell Shaw
2006-01-09 19:12 ` Mark Kettenis
2006-01-10 11:29   ` Russell Shaw
2006-01-10 19:16     ` Mark Kettenis
2006-01-10 21:41       ` Daniel Jacobowitz
2006-01-11  1:21         ` Russell Shaw
2006-01-11  1:43           ` Larry Martell
2006-01-11  1:52             ` Russell Shaw
2006-01-11  4:19               ` Eli Zaretskii
2006-01-11  4:41                 ` Russell Shaw
2006-01-11  4:45                   ` Joel Brobecker
2006-01-11  4:57                     ` Russell Shaw [this message]
2006-01-11 14:39                   ` Larry Martell
2006-01-10 11:30   ` Russell Shaw
2006-11-30  3:26 ` Bapi
2006-11-30  4:52   ` Nick Roberts

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43C4903F.3010503@netspace.net.au \
    --to=rjshaw@netspace.net.au \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox