[Lldb-commits] [PATCH] D72086: [lldb] Fix that SBThread.GetStopDescription is returning strings with uninitialized memory at the end.

[Raphael Isemann via Phabricator via lldb-commits]

teemperor added a comment.

For reasons that are beyond my understanding this change seems to break 
`SBProcess.GetSTDOUT` in random tests like this:

  ======================================================================
  ERROR: test_change_value_dwarf (TestChangeValueAPI.ChangeValueAPITestCase)
     Exercise the SBValue::SetValueFromCString API.
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File 
"/home/teemperor/work/ci/llvm/lldb/packages/Python/lldbsuite/test/lldbtest.py", 
line 1732, in test_method
      return attrvalue(self)
    File 
"/home/teemperor/work/ci/llvm/lldb/packages/Python/lldbsuite/test/decorators.py",
 line 454, in wrapper
      func(*args, **kwargs)
    File 
"/home/teemperor/work/ci/llvm/lldb/packages/Python/lldbsuite/test/decorators.py",
 line 110, in wrapper
      func(*args, **kwargs)
    File 
"/home/teemperor/work/ci/llvm/lldb/packages/Python/lldbsuite/test/python_api/value/change_values/TestChangeValueAPI.py",
 line 149, in test_change_value
      stdout = process.GetSTDOUT(1000)
    File 
"/home/teemperor/work/ci/build/lib/python3.8/site-packages/lldb/__init__.py", 
line 8020, in GetSTDOUT
      return _lldb.SBProcess_GetSTDOUT(self, dst)
  SystemError: <built-in function SBProcess_GetSTDOUT> returned NULL without 
setting an error
  Config=x86_64-/home/teemperor/work/ci/build/bin/clang-10

Anyone got a clue what is going on here? It seems like these tests only fail 
when run in combination with some other tests as running them alone is fine.


CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D72086/new/

https://reviews.llvm.org/D72086



_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits