From: Willy Tarreau <willy@w.ods.org>
To: Breno <brenosp@brasilsec.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Force Coredump
Date: Mon, 24 Nov 2003 16:13:07 +0100 [thread overview]
Message-ID: <20031124151307.GA25193@alpha.home.local> (raw)
In-Reply-To: <002301c3b291$9a2f50a0$34dfa7c8@bsb.virtua.com.br>
On Mon, Nov 24, 2003 at 11:48:10AM -0200, Breno wrote:
> Done , but no coredump file
>
> %ulimit -c unlimited
> %./test
> Segmention fault
> %ls -lisa
> test* test.c
You also need read permissions on the executable itself (it must be dumpable).
BTW, have you checked /proc/sys/kernel/core* ? Perhaps there's a pattern which
references a directory in which you have no permissions ?
HTH,
Willy
next prev parent reply other threads:[~2003-11-24 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 13:15 Breno
2003-11-24 13:31 ` tim
2003-11-24 13:48 ` Breno
2003-11-24 15:13 ` Willy Tarreau [this message]
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=20031124151307.GA25193@alpha.home.local \
--to=willy@w.ods.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®