slydiman wrote:
#111033
https://github.com/llvm/llvm-project/pull/104238
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -3180,15 +3180,24 @@ void
CommandInterpreter::IOHandlerInputComplete(IOHandler &io_handler,
if ((result.Succeeded() &&
io_handler.GetFlags().Test(eHandleCommandFlagPrintResult)) ||
io_handler.GetFlags().Test(eHandleCommandFlagPrintErrors)) {
-// Display a
https://github.com/jasonmolenda created
https://github.com/llvm/llvm-project/pull/110965
The x86 assembly instruction scanner creates incorrect UnwindPlans when a
mid-function epilogue has a non-epilogue instruction in it.
The x86 instruction analysis which creates an UnwindPlan handles mid-fu
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Jason Molenda (jasonmolenda)
Changes
The x86 assembly instruction scanner creates incorrect UnwindPlans when a
mid-function epilogue has a non-epilogue instruction in it.
The x86 instruction analysis which creates an UnwindPlan handles mid
github-actions[bot] wrote:
:warning: C/C++ code formatter, clang-format found issues in your code.
:warning:
You can test this locally with the following command:
``bash
git-clang-format --diff c1343a29216f08ec762b3e58572e5c3e41f6f285
8deef52bd49a54c8ea23d97460641d01d0daf898 --e
Michael137 wrote:
Hmm actually currently doesn't quite do what I wanted..
https://github.com/llvm/llvm-project/pull/110856
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -112,8 +113,46 @@ void CommandReturnObject::SetError(Status error) {
}
void CommandReturnObject::SetError(llvm::Error error) {
- if (error)
+ // Retrieve any diagnostics.
+ error = llvm::handleErrors(std::move(error), [&](ExpressionErrorBase &error)
{
j
@@ -112,8 +113,46 @@ void CommandReturnObject::SetError(Status error) {
}
void CommandReturnObject::SetError(llvm::Error error) {
- if (error)
+ // Retrieve any diagnostics.
+ error = llvm::handleErrors(std::move(error), [&](ExpressionErrorBase &error)
{
+SetStatus(eRe
jimingham wrote:
I find this API confusing, and it seems very focused on pointing out errors in
commands that have some part of their text that gets submitted to a compiler.
The other obvious candidate for this feature is a general command parser
implementation that handles:
(lldb) process la
https://github.com/dzhidzhoev approved this pull request.
https://github.com/llvm/llvm-project/pull/111033
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Dmitry Vasilyev
Date: 2024-10-03T22:23:12+04:00
New Revision: 000e790be35b77a01872851646d54432a203542c
URL:
https://github.com/llvm/llvm-project/commit/000e790be35b77a01872851646d54432a203542c
DIFF:
https://github.com/llvm/llvm-project/commit/000e790be35b77a01872851646d54432a203542c.dif
https://github.com/slydiman closed
https://github.com/llvm/llvm-project/pull/111033
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
101 - 112 of 112 matches
Mail list logo