From: tim@cambrant.com
To: Breno <brenosp@brasilsec.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Force Coredump
Date: Mon, 24 Nov 2003 14:31:20 +0100 [thread overview]
Message-ID: <20031124133120.GA13678@cambrant.com> (raw)
In-Reply-To: <001001c3b28d$183400e0$34dfa7c8@bsb.virtua.com.br>
On Mon, Nov 24, 2003 at 11:15:51AM -0200, Breno wrote:
> Anybody knows why ?
Perhaps you don't have writing access to the directory where the program is placed, or there is already a core file in the same directory, which you don't have writing access to. Another possibility (more likely) is that 'ulimit -c' is set too low. Try typing 'ulimit -c unlimited' and see if that works. This command will produce a core file for every segfault that occurs, which may be inconvenient, so take a note of what ulimit is set to before you change it.
Hope that helps. Good luck.
--
Tim Cambrant <tim@cambrant.com>
GPG KeyID 0x59518702
Fingerprint: 14FE 03AE C2D1 072A 87D0 BC4D FA9E 02D8 5951 8702
next prev parent reply other threads:[~2003-11-24 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 13:15 Force Coredump Breno
2003-11-24 13:31 ` tim [this message]
2003-11-24 13:48 ` Breno
2003-11-24 15:13 ` Willy Tarreau
2003-11-24 14:06 ` Jan-Benedict Glaw
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=20031124133120.GA13678@cambrant.com \
--to=tim@cambrant.com \
--cc=brenosp@brasilsec.com.br \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.