Re: [PATCH v2 1/4] test-tool: help verifying BUG() code paths

2018-05-05 Thread Johannes Schindelin
Hi Duy, On Wed, 2 May 2018, Duy Nguyen wrote: > On Wed, May 2, 2018 at 11:38 AM, Johannes Schindelin > wrote: > > When we call BUG(), we signal via SIGABRT that something bad happened, > > dumping cores if so configured. In some setups these coredumps are > > redirected to some central place suc

Re: [PATCH v2 1/4] test-tool: help verifying BUG() code paths

2018-05-02 Thread Duy Nguyen
On Wed, May 2, 2018 at 11:38 AM, Johannes Schindelin wrote: > When we call BUG(), we signal via SIGABRT that something bad happened, > dumping cores if so configured. In some setups these coredumps are > redirected to some central place such as /proc/sys/kernel/core_pattern, > which is a good thin

[PATCH v2 1/4] test-tool: help verifying BUG() code paths

2018-05-02 Thread Johannes Schindelin
When we call BUG(), we signal via SIGABRT that something bad happened, dumping cores if so configured. In some setups these coredumps are redirected to some central place such as /proc/sys/kernel/core_pattern, which is a good thing. However, when we try to verify in our test suite that bugs are ca