Re: [Qemu-devel] [PATCH for-1.4] tests/test-string-input-visitor: Handle errors provoked by fuzz test

2013-02-04 Thread Luiz Capitulino
On Mon, 04 Feb 2013 08:48:57 +0100 Markus Armbruster wrote: > [Note cc: Luiz] > > Peter Maydell writes: > > > On 2 February 2013 21:37, Andreas Färber wrote: > >> Am 02.02.2013 22:19, schrieb Peter Maydell: > >>> It's OK and expected for visitors to return errors when presented with > >>> the

Re: [Qemu-devel] [PATCH for-1.4] tests/test-string-input-visitor: Handle errors provoked by fuzz test

2013-02-03 Thread Markus Armbruster
[Note cc: Luiz] Peter Maydell writes: > On 2 February 2013 21:37, Andreas Färber wrote: >> Am 02.02.2013 22:19, schrieb Peter Maydell: >>> It's OK and expected for visitors to return errors when presented with >>> the fuzz test's random data. This means the test harness needs to >>> handle them

Re: [Qemu-devel] [PATCH for-1.4] tests/test-string-input-visitor: Handle errors provoked by fuzz test

2013-02-02 Thread Peter Maydell
On 2 February 2013 21:37, Andreas Färber wrote: > Am 02.02.2013 22:19, schrieb Peter Maydell: >> It's OK and expected for visitors to return errors when presented with >> the fuzz test's random data. This means the test harness needs to >> handle them; check for and free any error after each visit

Re: [Qemu-devel] [PATCH for-1.4] tests/test-string-input-visitor: Handle errors provoked by fuzz test

2013-02-02 Thread Andreas Färber
Am 02.02.2013 22:19, schrieb Peter Maydell: > It's OK and expected for visitors to return errors when presented with > the fuzz test's random data. This means the test harness needs to > handle them; check for and free any error after each visitor call, > and only free the string returned by visit_

[Qemu-devel] [PATCH for-1.4] tests/test-string-input-visitor: Handle errors provoked by fuzz test

2013-02-02 Thread Peter Maydell
It's OK and expected for visitors to return errors when presented with the fuzz test's random data. This means the test harness needs to handle them; check for and free any error after each visitor call, and only free the string returned by visit_type_str if visit_type_str succeeded. This fixes a