[all-commits] [llvm/llvm-project] 0c5b63: [lldb] Fix failure in TestStackCoreScriptedProcess...
Med Ismail Bennani via All-commits
all-commits at lists.llvm.org
Wed Jun 21 10:57:34 PDT 2023
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 0c5b6320716b4761f2c4307bc95197be5717d132
https://github.com/llvm/llvm-project/commit/0c5b6320716b4761f2c4307bc95197be5717d132
Author: Med Ismail Bennani <ismail at bennani.ma>
Date: 2023-06-21 (Wed, 21 Jun 2023)
Changed paths:
M lldb/include/lldb/Utility/StructuredData.h
M lldb/source/Plugins/Process/scripted/ScriptedThread.cpp
M lldb/test/API/functionalities/scripted_process/TestStackCoreScriptedProcess.py
Log Message:
-----------
[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 at bennani.ma>
More information about the All-commits
mailing list