From: Andreas Schwab <schwab@suse.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36279@debbugs.gnu.org, mail@xuchunyang.me, npostavs@gmail.com
Subject: bug#36279: 26.2.90; (process-attributes nonexistent-pid) segmentation fault
Date: Wed, 19 Jun 2019 10:01:22 +0200 [thread overview]
Message-ID: <mvmo92u0zsd.fsf@suse.de> (raw)
In-Reply-To: <m2h88mkq9e.fsf@gmail.com> (Robert Pluim's message of "Wed, 19 Jun 2019 09:06:53 +0200")
On Jun 19 2019, Robert Pluim <rpluim@gmail.com> wrote:
> From a70ac9f644660a16fa871a9f6933c1344ffae083 Mon Sep 17 00:00:00 2001
> From: Robert Pluim <rpluim@gmail.com>
> Date: Wed, 19 Jun 2019 08:52:50 +0200
> Subject: [PATCH] Check length returned by sysctl
> To: emacs-devel@gnu.org
>
> sysctl sometimes returns successfully even when it returns no data,
> such as when querying non-existent processes, which can cause crashes.
I thinks that's not a sometimes, but how it is documented to work.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2019-06-19 8:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 13:25 bug#36279: 26.2.90; (process-attributes nonexistent-pid) segmentation fault Xu Chunyang
2019-06-18 13:31 ` Noam Postavsky
2019-06-18 14:05 ` xuchunyang
2019-06-18 15:23 ` Robert Pluim
2019-06-18 16:23 ` xuchunyang
2019-06-18 17:44 ` Eli Zaretskii
2019-06-18 17:53 ` Robert Pluim
2019-06-18 18:06 ` Eli Zaretskii
2019-06-18 18:14 ` Robert Pluim
2019-06-19 7:06 ` Robert Pluim
2019-06-19 8:01 ` Andreas Schwab [this message]
2019-06-19 10:21 ` Robert Pluim
2019-06-19 10:29 ` Andreas Schwab
2019-06-19 13:40 ` Robert Pluim
2019-06-19 15:15 ` Eli Zaretskii
2019-06-20 8:46 ` Robert Pluim
2019-06-18 16:10 ` Eli Zaretskii
2019-06-18 16:07 ` Eli Zaretskii
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=mvmo92u0zsd.fsf@suse.de \
--to=schwab@suse.de \
--cc=36279@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mail@xuchunyang.me \
--cc=npostavs@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.