We can provide this via StopReason->GetValue(). This is important so that users of SB API can treat various sanitizers differently (the extended stop reason data is also structured differently for different sanitizers).
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
I am fine as long is Jim Ingham is fine. Jim, if you are good with this, just put it into Accept Revision.
Comment Actions
Aargh, sorry. My queue is overflowing... I had one tiny comment about the tests. If you do that, then it will be fine to go in.
packages/Python/lldbsuite/test/functionalities/asan/TestMemoryHistory.py | ||
---|---|---|
126–132 | Can you add a check that GetStopReasonDataCount and only do the check for GetStopReasonDataAtIndex if this is 1? We have the ability to run the testsuite against older lldb's and it's good not to add failures if it can be avoided. Plus it's good to check that that call is returning a reasonable value. | |
packages/Python/lldbsuite/test/functionalities/asan/TestReportData.py | ||
65–67 | Same comment as above. | |
packages/Python/lldbsuite/test/functionalities/tsan/basic/TestTsanBasic.py | ||
57–59 | Same comment as above. |
Can you add a check that GetStopReasonDataCount and only do the check for GetStopReasonDataAtIndex if this is 1? We have the ability to run the testsuite against older lldb's and it's good not to add failures if it can be avoided. Plus it's good to check that that call is returning a reasonable value.