From: Eugene Surovegin <ebs@ebshome.net>
To: David Ho <DavidHo@nanometrics.ca>
Cc: linuxppc <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: no core dump from the kernel on SIGSEGV
Date: Tue, 1 Jun 2004 14:18:47 -0700 [thread overview]
Message-ID: <20040601211846.GB17412@gate.ebshome.net> (raw)
In-Reply-To: <OF256E275C.8F4C3907-ON85256EA6.006EE439-85256EA6.006FEE36@nanometrics.ca>
On Tue, Jun 01, 2004 at 04:22:34PM -0400, David Ho wrote:
>
> Hi all,
>
> I'm looking at making the kernel core dump on a process that seg vaulted.
> What I did was recompiled the kernel specifying a non-zero core file size
> rlim[RLIMIT_CORE] = { RLIM_INFINITY, RLIM_INFINITY }. I was still not
> getting a core dump.
>
DO NOT TOUCH the kernel!
Please, read about ulimit shell command.
Eugene
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-01 21:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 14:18 driver SPI for MPC5200 iida
2004-06-01 17:37 ` Wolfgang Denk
2004-06-01 20:22 ` no core dump from the kernel on SIGSEGV David Ho
2004-06-01 21:18 ` Eugene Surovegin [this message]
2004-06-01 21:41 ` David Ho
2004-06-04 7:58 ` driver SPI for MPC5200 Kate Alhola
[not found] <OF096B1DBE.952B9CCB-ON85256EA6.0076D881-85256EA6.00771DCE@LocalDomain>
2004-06-01 22:07 ` no core dump from the kernel on SIGSEGV David Ho
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=20040601211846.GB17412@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=DavidHo@nanometrics.ca \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).