From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: FVWM taskbar segfault on ~amd64
Date: Sat, 1 Mar 2008 01:55:28 +0000 (UTC) [thread overview]
Message-ID: <pan.2008.03.01.01.55.28@cox.net> (raw)
In-Reply-To: 20080229170308.GA6121@crowfix.com
felix@crowfix.com posted 20080229170308.GA6121@crowfix.com, excerpted
below, on Fri, 29 Feb 2008 09:03:08 -0800:
> Now I feel like some dinosaurish fool here. I cannot get a core dump.
> ulimit -c 90000 or -c 1 or -c unlimited tells me
>
> -bash: ulimit: core file size: cannot modify limit: Operation not
> permitted
>
> Setting ulimit in /etc/profile doesn't give me a core dump, in $HOME or
> /tmp or anywhere that I can find. Bash's help ulimit says nothing about
> this. I can't find anything in /etc/sysctl.conf which disables core
> files. Changing /etc/security/limits.conf didn't help.
You probably checked it but if you mentioned it I missed it. Does your
kernel include corefile functionality? I have that option turned
entirely off, here. If likewise there, that might explain not being
able to turn it on from user mode.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-amd64@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-01 2:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 5:24 [gentoo-amd64] FVWM taskbar segfault on ~amd64 felix
2008-02-21 5:41 ` Jesús Guerrero
2008-02-21 16:26 ` felix
2008-02-21 18:44 ` Jesús Guerrero
2008-02-21 19:04 ` felix
2008-02-21 19:42 ` Jesús Guerrero
2008-02-21 21:08 ` Sebastian Redl
2008-02-21 21:47 ` felix
2008-02-21 21:54 ` felix
2008-02-21 22:40 ` Jesús Guerrero
2008-02-21 23:00 ` felix
2008-02-28 8:33 ` felix
2008-02-28 18:57 ` Jesús Guerrero
2008-02-29 6:48 ` felix
2008-02-29 14:55 ` Jesús Guerrero
2008-02-29 17:03 ` felix
2008-03-01 1:55 ` Duncan [this message]
2008-03-01 15:33 ` [gentoo-amd64] " felix
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=pan.2008.03.01.01.55.28@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@lists.gentoo.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