On 10 April 2014 08:10, Pekka Paalanen wrote:
> On Wed, 9 Apr 2014 16:44:53 +0200
> Marek Chalupa wrote:
>
> > bad-buffer-test is FAIL_TEST and every assert() (or even SIGSEGV signal)
> > make it pass. It shouldn't be so for example when assert() is invoked
> > when a client couldn't connect to
On Wed, 9 Apr 2014 16:44:53 +0200
Marek Chalupa wrote:
> bad-buffer-test is FAIL_TEST and every assert() (or even SIGSEGV signal)
> make it pass. It shouldn't be so for example when assert() is invoked
> when a client couldn't connect to display.
>
> Make sure that only relevant asserts make th
bad-buffer-test is FAIL_TEST and every assert() (or even SIGSEGV signal)
make it pass. It shouldn't be so for example when assert() is invoked
when a client couldn't connect to display.
Make sure that only relevant asserts make the test pass
and the other make it fail (by returning 0)
---
tests/b
