From: "Pádraig Brady" <P@draigBrady.com>
To: "Voelker, Bernhard" <bernhard.voelker@siemens-enterprise.com>
Cc: Ondrej Oprala <ooprala@redhat.com>,
"util-linux@vger.kernel.org" <util-linux@vger.kernel.org>
Subject: Re: segfault message supressed with su -c
Date: Tue, 11 Sep 2012 19:02:02 +0100 [thread overview]
Message-ID: <504F7C9A.1000904@draigBrady.com> (raw)
In-Reply-To: <A75C39900FCF0B42A2CE8B26F837D2C305BB3C@MCHP02MSX.global-ad.net>
On 09/11/2012 05:19 PM, Voelker, Bernhard wrote:
> Ondrej Oprala wrote:
>> Hi,
>> I've written a tiny patch that should fix this issue with su:
>> https://bugzilla.redhat.com/show_bug.cgi?id=747592.
>> None of the shells' output propagates back
>> to the shell where su was called (except TCSH, which reports segfault
>> to stdout; I've tested this with sh,ksh,zsh,bash).
>> So, with this patch, su should print a warning if
>> WIFSIGNALED(status)&& WCOREDUMP(status) is true.
>
> Good catch!
>
>> + fprintf (stderr, _("Segmentation fault (core dumped)\n"));
>
> Maybe the error message should point out that it
> was not su which dumped core ... ;-)
Maybe not. Consider:
monitor_1 timeout 2 'su -c command'
You might as well just say "core dumped",
and leave the investigation as to what
cored exactly to inspection of the core file.
cheers,
Pádraig.
next prev parent reply other threads:[~2012-09-11 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 15:01 segfault message supressed with su -c Ondrej Oprala
2012-09-11 16:19 ` Voelker, Bernhard
2012-09-11 18:02 ` Pádraig Brady [this message]
2012-09-11 17:19 ` Pádraig Brady
2012-09-12 10:22 ` Ondrej Oprala
2012-09-21 10:39 ` Karel Zak
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=504F7C9A.1000904@draigBrady.com \
--to=p@draigbrady.com \
--cc=bernhard.voelker@siemens-enterprise.com \
--cc=ooprala@redhat.com \
--cc=util-linux@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.