diff options
author | Med Ismail Bennani <ismail@bennani.ma> | 2023-06-13 13:47:14 -0700 |
---|---|---|
committer | Med Ismail Bennani <ismail@bennani.ma> | 2023-06-21 10:57:13 -0700 |
commit | 0c5b6320716b4761f2c4307bc95197be5717d132 (patch) | |
tree | 213eab99e59ebea9db4f06e790043a1fc26418cc /llvm/lib/CodeGen/MachineBlockPlacement.cpp | |
parent | 63538a087926f9f9dc992918b06be4720f4c59fb (diff) | |
download | llvm-0c5b6320716b4761f2c4307bc95197be5717d132.zip llvm-0c5b6320716b4761f2c4307bc95197be5717d132.tar.gz llvm-0c5b6320716b4761f2c4307bc95197be5717d132.tar.bz2 |
[lldb] Fix failure in TestStackCoreScriptedProcess on x86_64
This patch should address the failure of TestStackCoreScriptedProcess
that is happening specifically on x86_64.
It turns out that in 1370a1cb5b97, I changed the way we extract integers
from a `StructuredData::Dictionary` and in order to get a stop info from
the scripted process, we call a method that returns a `SBStructuredData`
containing the stop reason data.
TestStackCoreScriptedProcess` was failing specifically on x86_64 because
the stop info dictionary contains the signal number, that the `Scripted
Thread` was trying to extract as a signed integer where it was actually
parsed as an unsigned integer. That caused `GetValueForKeyAsInteger` to
return the default value parameter, `LLDB_INVALID_SIGNAL_NUMBER`.
This patch address the issue by extracting the signal number with the
appropriate type and re-enables the test.
Differential Revision: https://reviews.llvm.org/D152848
Signed-off-by: Med Ismail Bennani <ismail@bennani.ma>
Diffstat (limited to 'llvm/lib/CodeGen/MachineBlockPlacement.cpp')
0 files changed, 0 insertions, 0 deletions