| #
36de94cf |
| 18-Dec-2020 |
Tatyana Krasnukha <[email protected]> |
Reland "[lldb] Make CommandInterpreter's execution context the same as debugger's one"
|
| #
122a4ebd |
| 17-Dec-2020 |
Pavel Labath <[email protected]> |
Revert "[lldb] Make CommandInterpreter's execution context the same as debugger's one."
This reverts commit a01b26fb51c710a3a8ef88cc83b0701461f5b9ab, because it breaks the "finish" command in some w
Revert "[lldb] Make CommandInterpreter's execution context the same as debugger's one."
This reverts commit a01b26fb51c710a3a8ef88cc83b0701461f5b9ab, because it breaks the "finish" command in some way -- the command does not terminate after it steps out, but continues running the target. The exact blast radius is not clear, but it at least affects the usage of the "finish" command in TestGuiBasicDebug.py. The error is *not* gui-related, as the same issue can be reproduced by running the same steps outside of the gui.
There is some kind of a race going on, as the test fails only 20% of the time on the buildbot.
show more ...
|
| #
a01b26fb |
| 10-Dec-2020 |
Tatyana Krasnukha <[email protected]> |
[lldb] Make CommandInterpreter's execution context the same as debugger's one.
Currently, the interpreter's context is not updated until a command is executed. This has resulted in the behavior of S
[lldb] Make CommandInterpreter's execution context the same as debugger's one.
Currently, the interpreter's context is not updated until a command is executed. This has resulted in the behavior of SB-interface functions and some commands depends on previous user actions. The interpreter's context can stay uninitialized, point to a currently selected target, or point to one of previously selected targets.
This patch removes any usages of CommandInterpreter::UpdateExecutionContext. CommandInterpreter::HandleCommand* functions still may override context temporarily, but now they always restore it before exiting. CommandInterpreter saves overriden contexts to the stack, that makes nesting commands possible.
Added test reproduces one of the issues. Without this fix, the last assertion fails because interpreter's execution context is empty until running "target list", so, the value of the global property was updated instead of process's local instance.
Differential Revision: https://reviews.llvm.org/D92164
show more ...
|
| #
f7e04b71 |
| 03-Sep-2020 |
Jordan Rupprecht <[email protected]> |
[lldb/Gui] zero-initialize children_stop_id
This is currently causing msan warnings in the API tests when run under msan, e.g. `commands/gui/basic/TestGuiBasic.py`.
Reviewed By: clayborg
Different
[lldb/Gui] zero-initialize children_stop_id
This is currently causing msan warnings in the API tests when run under msan, e.g. `commands/gui/basic/TestGuiBasic.py`.
Reviewed By: clayborg
Differential Revision: https://reviews.llvm.org/D86825
show more ...
|
| #
dcd4589a |
| 05-Aug-2020 |
Luboš Luňák <[email protected]> |
[lldb][gui] use left/right in the source view to scroll
I intentionally decided not to reset the column automatically anywhere, because I don't know where and if at all that should happen. There sho
[lldb][gui] use left/right in the source view to scroll
I intentionally decided not to reset the column automatically anywhere, because I don't know where and if at all that should happen. There should be always an indication of being scrolled (too much) to the right, so I'll leave this to whoever has an opinion.
Differential Revision: https://reviews.llvm.org/D85290
show more ...
|
| #
9dbdaea9 |
| 06-Aug-2020 |
Sterling Augustine <[email protected]> |
Remove unused variable "saved_opts".
wattr_get is a macro, and the documentation states: "The parameter opts is reserved for future use, applications must supply a null pointer."
In practice, pass
Remove unused variable "saved_opts".
wattr_get is a macro, and the documentation states: "The parameter opts is reserved for future use, applications must supply a null pointer."
In practice, passing a variable there is harmless, except that it is unused inside the macro, which causes unused variable warnings.
The various places where
show more ...
|
| #
d40c44e8 |
| 06-Aug-2020 |
Raphael Isemann <[email protected]> |
[lldb] Fix LLDB compilation with ncurses 6.2 due to wattr_set/get being a macro
My ncurses 6.2 arch defines those two functions as macros, so the scope operator doesn't work here.
|
| #
4a8e4b5c |
| 05-Aug-2020 |
Luboš Luňák <[email protected]> |
[lldb][gui] use names for color pairs, instead of magic numbers
Differential Revision: https://reviews.llvm.org/D85286
|
| #
14406ca0 |
| 04-Aug-2020 |
Luboš Luňák <[email protected]> |
[lldb][gui] use syntax highlighting also in gui mode
Use the same functionality as the non-gui mode, the colors just need translating to curses colors.
Differential Revision: https://reviews.llvm.o
[lldb][gui] use syntax highlighting also in gui mode
Use the same functionality as the non-gui mode, the colors just need translating to curses colors.
Differential Revision: https://reviews.llvm.org/D85145
show more ...
|
| #
fc0e8fb7 |
| 03-Aug-2020 |
Luboš Luňák <[email protected]> |
[lldb][gui] truncate long lines/names if needed
Without this, sources with long lines or variable names may overwrite panel frames, or even overrun to the following line. There's currently no way to
[lldb][gui] truncate long lines/names if needed
Without this, sources with long lines or variable names may overwrite panel frames, or even overrun to the following line. There's currently no way to scroll left/right in the views, so that should be added to handle these cases. This commit includes fixing constness of some Window functions, and also makes PutCStringTruncated() consistent with the added printf-like variant to take the padding as the first argument (can't add it after the format to the printf-like function).
Differential Revision: https://reviews.llvm.org/D85123
show more ...
|
| #
d6868d9c |
| 02-Aug-2020 |
Luboš Luňák <[email protected]> |
[lldb][gui] implement breakpoint removal on breakpoint toggling
It says it toggles breakpoints, so if one already exists on the selected location, remove it instead of adding.
Differential Revision
[lldb][gui] implement breakpoint removal on breakpoint toggling
It says it toggles breakpoints, so if one already exists on the selected location, remove it instead of adding.
Differential Revision: https://reviews.llvm.org/D85098
show more ...
|
| #
7a63dc53 |
| 02-Aug-2020 |
Luboš Luňák <[email protected]> |
[lldb][gui] implement shift+tab for going back in views
Also simplify the code for going forward.
Differential Revision: https://reviews.llvm.org/D85089
|
| #
2f1b24b7 |
| 02-Aug-2020 |
Luboš Luňák <[email protected]> |
[lldb][gui] implement TerminalSizeChanged()
Differential Revision: https://reviews.llvm.org/D85088
|
| #
c952ec15 |
| 04-Aug-2020 |
Luboš Luňák <[email protected]> |
[lldb] fix building with panel.h being in /usr/include/ncurses/
My openSUSE 15.2 has /usr/include/curses.h as a symlink to /usr/include/ncurses/curses.h , but there's no such symlink for panel.h . P
[lldb] fix building with panel.h being in /usr/include/ncurses/
My openSUSE 15.2 has /usr/include/curses.h as a symlink to /usr/include/ncurses/curses.h , but there's no such symlink for panel.h . Prefer using /usr/include/ncurses for the includes if they are found there by the CMake check.
Differential Revision: https://reviews.llvm.org/D85219
show more ...
|
| #
daa1c6d9 |
| 04-Aug-2020 |
Luboš Luňák <[email protected]> |
[lldb] fix typo
|
| #
8739445e |
| 30-Jul-2020 |
Luboš Luňák <[email protected]> |
[lldb] force full gui redraw on Ctrl+L
As is common with curses apps, this allows to redraw everything in case something corrupts the screen. Apparently key modifiers are difficult with curses (curs
[lldb] force full gui redraw on Ctrl+L
As is common with curses apps, this allows to redraw everything in case something corrupts the screen. Apparently key modifiers are difficult with curses (curses FAQ it "doesn't do that"), thankfully Ctrl+key are simply control characters, so it's (ascii & 037) => 12.
Differential Revision: https://reviews.llvm.org/D84972
show more ...
|
|
Revision tags: llvmorg-11.0.0-rc1, llvmorg-12-init, llvmorg-10.0.1, llvmorg-10.0.1-rc4, llvmorg-10.0.1-rc3, llvmorg-10.0.1-rc2, llvmorg-10.0.1-rc1, llvmorg-10.0.0, llvmorg-10.0.0-rc6, llvmorg-10.0.0-rc5, llvmorg-10.0.0-rc4, llvmorg-10.0.0-rc3, llvmorg-10.0.0-rc2, llvmorg-10.0.0-rc1, llvmorg-11-init, llvmorg-9.0.1, llvmorg-9.0.1-rc3, llvmorg-9.0.1-rc2, llvmorg-9.0.1-rc1 |
|
| #
13978643 |
| 05-Oct-2019 |
Luboš Luňák <[email protected]> |
[lldb] implement 'up' and 'down' shortcuts in lldb gui
Also add a unittest.
Differential Revision: https://reviews.llvm.org/D68541
|
| #
336c7029 |
| 11-Oct-2019 |
Luboš Luňák <[email protected]> |
[lldb] change shortcut for 'step out' from 'o' to 'f'
This makes it consistent with gdb tui, where 'f' is 'finish'. See the discussion at https://reviews.llvm.org/D68541 .
Differential Revision: ht
[lldb] change shortcut for 'step out' from 'o' to 'f'
This makes it consistent with gdb tui, where 'f' is 'finish'. See the discussion at https://reviews.llvm.org/D68541 .
Differential Revision: https://reviews.llvm.org/D68909
show more ...
|
| #
47d2c7cd |
| 11-Oct-2019 |
Luboš Luňák <[email protected]> |
[lldb] remove somewhat dangerous 'd'(etach) and 'k'(ill) shortcuts
'd' would be much better used for up/down shortcuts, and this also removes the possibility of ruining the whole debugging session b
[lldb] remove somewhat dangerous 'd'(etach) and 'k'(ill) shortcuts
'd' would be much better used for up/down shortcuts, and this also removes the possibility of ruining the whole debugging session by accidentally hitting 'd' or 'k'. Also change menu to have both 'detach and resume' and 'detach suspended' to make it clear which one is which. See discussion at https://reviews.llvm.org/D68541 .
Differential Revision: https://reviews.llvm.org/D68908
show more ...
|
| #
cee60bbf |
| 23-Jul-2020 |
Jonas Devlieghere <[email protected]> |
[lldb] Remove the user-defined copy-ctor in ConstString
ConstString is essentially trivially copyable yet it has a user defined copy constructor that copies its one member pointer. Remove it so it q
[lldb] Remove the user-defined copy-ctor in ConstString
ConstString is essentially trivially copyable yet it has a user defined copy constructor that copies its one member pointer. Remove it so it qualifies as trivial in the eyes of the compiler.
This also fixes two unused variable warnings now that the compiler knows that the constructor has no side-effects.
Differential revision: https://reviews.llvm.org/D84440
show more ...
|
| #
06412dae |
| 25-Jun-2020 |
Jonas Devlieghere <[email protected]> |
[lldb] Use std::make_unique<> (NFC)
Update the rest of lldb to use std::make_unique<>. I used clang-tidy to automate this, which probably missed cases that are wrapped in ifdefs.
|
| #
f5eaa2af |
| 19-Jun-2020 |
Raphael Isemann <[email protected]> |
[lldb] Replace std::isprint/isspace with llvm's locale-independent version
Summary: LLVM is using its own isPrint/isSpace implementation that doesn't change depending on the current locale. LLDB sho
[lldb] Replace std::isprint/isspace with llvm's locale-independent version
Summary: LLVM is using its own isPrint/isSpace implementation that doesn't change depending on the current locale. LLDB should do the same to prevent that internal logic changes depending on the set locale.
Reviewers: JDevlieghere, labath, mib, totally_not_teemperor
Reviewed By: JDevlieghere
Differential Revision: https://reviews.llvm.org/D82175
show more ...
|
| #
eaebcbc6 |
| 02-Jun-2020 |
Konrad Kleine <[email protected]> |
[lldb] NFC remove DISALLOW_COPY_AND_ASSIGN
Summary: This is how I applied my clang-tidy check (see https://reviews.llvm.org/D80531) in order to remove `DISALLOW_COPY_AND_ASSIGN` and have deleted cop
[lldb] NFC remove DISALLOW_COPY_AND_ASSIGN
Summary: This is how I applied my clang-tidy check (see https://reviews.llvm.org/D80531) in order to remove `DISALLOW_COPY_AND_ASSIGN` and have deleted copy ctors and deleted assignment operators instead.
``` lang=bash grep DISALLOW_COPY_AND_ASSIGN /opt/notnfs/kkleine/llvm/lldb -r -l | sort | uniq > files
for i in $(cat files); do clang-tidy \ --checks="-*,modernize-replace-disallow-copy-and-assign-macro" \ --format-style=LLVM \ --header-filter=.* \ --fix \ -fix-errors \ $i; done ```
Reviewers: espindola, labath, aprantl, teemperor
Reviewed By: labath, aprantl, teemperor
Subscribers: teemperor, aprantl, labath, emaste, sbc100, aheejin, MaskRay, arphaman, usaxena95, lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D80543
show more ...
|
| #
80814287 |
| 24-Jan-2020 |
Raphael Isemann <[email protected]> |
[lldb][NFC] Fix all formatting errors in .cpp file headers
Summary: A *.cpp file header in LLDB (and in LLDB) should like this: ``` //===-- TestUtilities.cpp ----------------------------------------
[lldb][NFC] Fix all formatting errors in .cpp file headers
Summary: A *.cpp file header in LLDB (and in LLDB) should like this: ``` //===-- TestUtilities.cpp -------------------------------------------------===// ``` However in LLDB most of our source files have arbitrary changes to this format and these changes are spreading through LLDB as folks usually just use the existing source files as templates for their new files (most notably the unnecessary editor language indicator `-*- C++ -*-` is spreading and in every review someone is pointing out that this is wrong, resulting in people pointing out that this is done in the same way in other files).
This patch removes most of these inconsistencies including the editor language indicators, all the different missing/additional '-' characters, files that center the file name, missing trailing `===//` (mostly caused by clang-format breaking the line).
Reviewers: aprantl, espindola, jfb, shafik, JDevlieghere
Reviewed By: JDevlieghere
Subscribers: dexonsmith, wuzish, emaste, sdardis, nemanjai, kbarton, MaskRay, atanasyan, arphaman, jfb, abidh, jsji, JDevlieghere, usaxena95, lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D73258
show more ...
|
| #
a4304f96 |
| 12-Dec-2019 |
Jonas Devlieghere <[email protected]> |
[lldb/CMake] Rename LLDB_DISABLE_CURSES to LLDB_ENABLE_CURSES
This matches the naming scheme used by LLVM.
Differential revision: https://reviews.llvm.org/D71377
|