1. 19 6月, 2014 3 次提交
  2. 09 5月, 2014 1 次提交
  3. 18 2月, 2014 1 次提交
  4. 07 2月, 2013 1 次提交
    • P
      tests/test-string-input-visitor: Handle errors provoked by fuzz test · 01845438
      Peter Maydell 提交于
      It's OK and expected for visitors to return errors when presented with
      the fuzz test's random data. Since the fuzzer doesn't care about
      errors, we pass in NULL rather than an Error**. This fixes a bug in
      the fuzzer where it was passing the same Error** into each visitor,
      with the effect that once one visitor returned an error, each later
      visitor would notice that it had been passed in an Error** representing
      an already set error, and do nothing.
      
      For the case of visit_type_str() we also need to handle the case where
      an error means that the visitor doesn't set our char*. We initialize
      the pointer to NULL so we can safely g_free() it regardless of whether
      the visitor allocated a string for us or not.
      
      This fixes a problem where this test failed the MacOSX malloc()
      consistency checks and might segfault on other platforms [due
      to calling free() on an uninitialized pointer variable when
      visit_type_str() failed.].
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      Reviewed-by: NAndreas Färber <afaerber@suse.de>
      Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
      01845438
  5. 26 1月, 2013 1 次提交
  6. 19 12月, 2012 2 次提交
  7. 30 3月, 2012 1 次提交
  8. 21 2月, 2012 1 次提交