From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: peter.maydell@linaro.org, mst@redhat.com, f4bug@amsat.org,
qemu-devel@nongnu.org, alex.bennee@linaro.org, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v2 for-3.0] tests/libqtest: Improve kill_qemu()
Date: Mon, 30 Jul 2018 16:24:55 -0500 [thread overview]
Message-ID: <a5c7582a-419a-03fb-4f05-c59fed4f0732@redhat.com> (raw)
In-Reply-To: <878t5zxpc2.fsf@dusky.pond.sub.org>
On 07/25/2018 11:17 AM, Markus Armbruster wrote:
>>
>> the output was produced by bash, which uses waitpid() - and therefore
>> the fact that bash reports the core dump even when no core file is
>> created is promising.
>
> Proof beats plausibility argument:
>
> $ cat wcordump.c
> $ gcc -Wall -g -O wcordump.c
> $ (ulimit -c unlimited; ./a.out)
> sig 6 128
> $ (ulimit -c 0; ./a.out)
> sig 6 0
Doesn't match my results:
$ (ulimit -c 0; ./a.out)
sig 6 128
So, what's different between our two environments?
kernel 4.17.7-100.fc27.x86_64
$ echo /proc/sys/kernel/core_*
/proc/sys/kernel/core_pattern /proc/sys/kernel/core_pipe_limit
/proc/sys/kernel/core_uses_pid
$ cat /proc/sys/kernel/core_*
|/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %e
0
1
>
> Looks like WCOREDUMP() does depend on my ulimit -c.
Or worse, that its behavior is kernel/environment-sensitive.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-07-30 21:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 19:35 [Qemu-devel] [PATCH v2 for-3.0] tests/libqtest: Improve kill_qemu() Eric Blake
2018-07-23 20:20 ` Richard Henderson
2018-07-24 6:36 ` Markus Armbruster
2018-07-24 14:35 ` Eric Blake
2018-07-25 16:17 ` Markus Armbruster
2018-07-30 21:24 ` Eric Blake [this message]
2018-07-31 5:35 ` Markus Armbruster
2018-07-24 6:44 ` Thomas Huth
2018-07-30 21:26 ` Eric Blake
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=a5c7582a-419a-03fb-4f05-c59fed4f0732@redhat.com \
--to=eblake@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=f4bug@amsat.org \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).