From: Sean Neakums <sneakums@zork.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Coredump file
Date: Sun, 23 Nov 2003 22:09:43 +0000 [thread overview]
Message-ID: <6ud6birb2w.fsf@zork.zork.net> (raw)
In-Reply-To: <000c01c3b20b$a4857560$34dfa7c8@bsb.virtua.com.br> (brenosp@brasilsec.com.br's message of "Sun, 23 Nov 2003 19:49:15 -0200")
"Breno" <brenosp@brasilsec.com.br> writes:
> How can I generate a coredump file ?
> I tryed to force a signal "Quit" , using ^\ , but didn´t work.
Here are some possible reasons for this:
* the core dump ulimit may be set too low (check this with ulimit -c)
* you do not have write permission for the process's cwd
* there is a core file in the process's cwd that you do not own
prev parent reply other threads:[~2003-11-23 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-23 21:49 Breno
2003-11-23 22:09 ` Sean Neakums [this message]
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=6ud6birb2w.fsf@zork.zork.net \
--to=sneakums@zork.net \
--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®