lldb/test/API/python_api/exprpath_synthetic/TestExprPathSynthetic.py

from lldbsuite.test import decorators
from lldbsuite.test import lldbinline

lldbinline.MakeInlineTest(__file__, globals(), [decorators.skipUnlessDarwin])
Move the rest of the tests over to using the new decorator module. llvm-svn: 259838 2016-02-04 23:04:17 +00:00			`from lldbsuite.test import decorators`
			`from lldbsuite.test import lldbinline`
Extend ValueObject::GetExpressionPath() to do something reasonable for synthetic children Because of the way they are created, synthetic children cannot (in general) have a sane expression path A solution to this would be letting the parent front-end generate expression paths for its children Doing so requires a significant amount of refactoring, and might not always lead to better results (esp. w.r.t. C++ templates) This commit takes a simpler approach: - if a synthetic child is of pointer type and it's a target pointer, then emit ((T)value) - if a synthetic child is a non-pointer, but its location is in the target, then emit ((T*)loadAddr) - if a synthetic child has a value, emit ((T)value) - else, don't emit anything Fixes rdar://18442386 llvm-svn: 223836 2014-12-09 21:41:16 +00:00
[lldb] [test] Use skipUnlessDarwin for tests specific to Darwin Use skipUnlessDarwin decorator for tests that are specific to Darwin, instead of skipIf... for all other platforms. This should make it clear that these tests are not supposed to work elsewhere. It will also make these tests stop repeatedly popping up while I look for tests that could be fixed on the platform in question. Differential Revision: https://reviews.llvm.org/D91003 2020-11-07 17:12:57 +01:00			`lldbinline.MakeInlineTest(__file__, globals(), [decorators.skipUnlessDarwin])`