From: Eli Zaretskii <eliz@gnu.org>
To: Russell Shaw <rjshaw@netspace.net.au>
Cc: gdb@sources.redhat.com
Subject: Re: Core dumps
Date: Wed, 11 Jan 2006 04:19:00 -0000 [thread overview]
Message-ID: <uu0cbqtvb.fsf@gnu.org> (raw)
In-Reply-To: <43C464D2.4000107@netspace.net.au> (message from Russell Shaw on Wed, 11 Jan 2006 12:52:18 +1100)
> Date: Wed, 11 Jan 2006 12:52:18 +1100
> From: Russell Shaw <rjshaw@netspace.net.au>
> Cc: gdb@sources.redhat.com
>
> > Doesn't a SIGABRT (kill -6) force a core dump?
>
> I put this in my own code, but it still doesn't make a
> core file:
>
> printf("Aborting...\n");
> raise(6);
Probably because your shell's init file(s) specify that the limit on
core files is zero bytes. Use `ulimit' to change that to `unlimited'.
next prev parent reply other threads:[~2006-01-11 4:19 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 [this message]
2006-01-11 4:41 ` Russell Shaw
2006-01-11 4:45 ` Joel Brobecker
2006-01-11 4:57 ` Russell Shaw
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=uu0cbqtvb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=rjshaw@netspace.net.au \
/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