All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 216648] man 5 core incorrectly states circumstances in which a core is not produced
Date: Tue, 01 Nov 2022 14:51:06 +0000	[thread overview]
Message-ID: <bug-216648-11311-1xpuZrs2EW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216648-11311@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216648

--- Comment #2 from Luca Versari (veluca93@gmail.com) ---
> Do you have any experiments demonstrating the actual behavior? Could you show
> them?
On a system with systemd (or where /proc/sys/kernel/core_pattern is configured
to pipe to a program), run `ulimit -c 0`, then run a program that segfaults
(writing `int main() { *(volatile int *)0; }` in a `segfault.c` file and
running `gcc segfault.c; ./a.out` should be sufficient). This creates a core
dump, despite RLIMIT_CORE being 0.

> And do you suggest any specific patch for that page?
Something like adding ", unless the system is configured to pipe core dumps to
a program" in that bullet point should be sufficient.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-11-01 14:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 12:26 [Bug 216648] New: man 5 core incorrectly states circumstances in which a core is not produced bugzilla-daemon
2022-11-01 14:28 ` [Bug 216648] " bugzilla-daemon
2022-11-01 14:51 ` bugzilla-daemon [this message]
2023-01-08  9:37 ` bugzilla-daemon

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=bug-216648-11311-1xpuZrs2EW@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-man@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.