Revision tags: llvmorg-18.1.8, llvmorg-18.1.7, llvmorg-18.1.6, llvmorg-18.1.5, llvmorg-18.1.4, llvmorg-18.1.3, llvmorg-18.1.2, llvmorg-18.1.1, llvmorg-18.1.0, llvmorg-18.1.0-rc4, llvmorg-18.1.0-rc3, llvmorg-18.1.0-rc2, llvmorg-18.1.0-rc1, llvmorg-19-init, llvmorg-17.0.6, llvmorg-17.0.5, llvmorg-17.0.4, llvmorg-17.0.3, llvmorg-17.0.2, llvmorg-17.0.1, llvmorg-17.0.0, llvmorg-17.0.0-rc4, llvmorg-17.0.0-rc3, llvmorg-17.0.0-rc2, llvmorg-17.0.0-rc1, llvmorg-18-init, llvmorg-16.0.6, llvmorg-16.0.5 |
|
#
2238dcc3 |
| 25-May-2023 |
Jonas Devlieghere <jonas@devlieghere.com> |
[NFC][Py Reformat] Reformat python files in lldb
This is an ongoing series of commits that are reformatting our Python code. Reformatting is done with `black` (23.1.0).
If you end up having problem
[NFC][Py Reformat] Reformat python files in lldb
This is an ongoing series of commits that are reformatting our Python code. Reformatting is done with `black` (23.1.0).
If you end up having problems merging this commit because you have made changes to a python file, the best way to handle that is to run `git checkout --ours <yourfile>` and then reformat it with black.
RFC: https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style
Differential revision: https://reviews.llvm.org/D151460
show more ...
|
Revision tags: llvmorg-16.0.4, llvmorg-16.0.3, llvmorg-16.0.2, llvmorg-16.0.1, llvmorg-16.0.0, llvmorg-16.0.0-rc4, llvmorg-16.0.0-rc3, llvmorg-16.0.0-rc2, llvmorg-16.0.0-rc1, llvmorg-17-init, llvmorg-15.0.7, llvmorg-15.0.6, llvmorg-15.0.5, llvmorg-15.0.4, llvmorg-15.0.3, working, llvmorg-15.0.2, llvmorg-15.0.1, llvmorg-15.0.0, llvmorg-15.0.0-rc3, llvmorg-15.0.0-rc2, llvmorg-15.0.0-rc1, llvmorg-16-init |
|
#
ba14e4d6 |
| 05-Jul-2022 |
Muhammad Omair Javaid <omair.javaid@linaro.org> |
[LLDB] Disable TestGdbRemoteFork* for Arm/AArch64 Linux
This test is causing some trouble with LLDB Arm/AArch64 Linux buildbot. I am disabling is temporarily to make buildbot green.
|
#
4a95861d |
| 29-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [test] Avoid relying on signos in other fork tests
Sponsored by: The FreeBSD Foundation
|
#
e60ed240 |
| 29-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [test] Un-XFAIL fork tests on arm as well
Sponsored by: The FreeBSD Foundation
|
#
251165b2 |
| 29-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [test] Use raise(SIGSTOP) instead of trap in fork tests
Replace the use of "trap" with a new "stop" command in fork tests, that maps to `raise(SIGSTOP)`. Since traps do not increment PC on s
[lldb] [test] Use raise(SIGSTOP) instead of trap in fork tests
Replace the use of "trap" with a new "stop" command in fork tests, that maps to `raise(SIGSTOP)`. Since traps do not increment PC on some architectures (notably ARM), using traps would require special logic to increment it while testing. Using SIGSTOP avoids the problem and is probably more logical, given that the purpose of the "trap"s was to simply stop the inferior at a synchronization point. This fixes tests on AArch64 (and possibly ARM, I'll update XFAILs when it is confirmed by the buildbot).
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D128780
show more ...
|
#
7fc12da8 |
| 29-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [test] Split TestGdbRemoteFork in two
Split the test that's gotten very long in two, in hope that it will resolve the arm/aarch64 buildbot failures. Even if it does not, it could help pinpoi
[lldb] [test] Split TestGdbRemoteFork in two
Split the test that's gotten very long in two, in hope that it will resolve the arm/aarch64 buildbot failures. Even if it does not, it could help pinpointing where the problem lies.
Sponsored by: The FreeBSD Foundation
show more ...
|
#
261d0033 |
| 27-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [llgs] Fix premature server exit if multiprocess+nonstop
Fix lldb-server in the non-stop + multiprocess mode to exit on vStopped only if all processes have exited, rather than when the first
[lldb] [llgs] Fix premature server exit if multiprocess+nonstop
Fix lldb-server in the non-stop + multiprocess mode to exit on vStopped only if all processes have exited, rather than when the first one exits.
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D128639
show more ...
|
#
b415f8e3 |
| 22-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [llgs] Add base nonstop fork/vfork tests
Extend the most of baseline fork tests to run in nonstop mode as well. For more cases, we're just testing one example scenario to save time. This patc
[lldb] [llgs] Add base nonstop fork/vfork tests
Extend the most of baseline fork tests to run in nonstop mode as well. For more cases, we're just testing one example scenario to save time. This patch does not cover tests that rely on correct exit handling, as fixing that is addressed in a followup patch.
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D128638
show more ...
|
#
25f46084 |
| 28-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [test] XFAIL llgs tests failing on arm
Sponsored by: The FreeBSD Foundation
|
#
a1df636a |
| 28-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [test] Skip llgs tests broken due to #56268 on aarch64
Sponsored by: The FreeBSD Foundation
|
#
1452e2e5 |
| 25-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
Reland "[lldb] [llgs] Support multiprocess in qfThreadInfo"
Now preserving the non-standard behavior of returning "OK" response when there is no debugged process.
Sponsored by: The FreeBSD Foundati
Reland "[lldb] [llgs] Support multiprocess in qfThreadInfo"
Now preserving the non-standard behavior of returning "OK" response when there is no debugged process.
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D128152
show more ...
|
#
f609b54e |
| 25-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
Revert "[lldb] [llgs] Support multiprocess in qfThreadInfo"
This reverts part of commit 75757c86c695a6b4695458343637b3c4fe86def6. It broke the following test:
commands/target/auto-install-main-ex
Revert "[lldb] [llgs] Support multiprocess in qfThreadInfo"
This reverts part of commit 75757c86c695a6b4695458343637b3c4fe86def6. It broke the following test:
commands/target/auto-install-main-executable/TestAutoInstallMainExecutable.py
I need more time to figure it out, so I'm reverting the code changes and marking the tests depending on them xfail.
show more ...
|
#
c1829e0e |
| 22-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [test] Move part of fork tests to common helper
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D128361
|
Revision tags: llvmorg-14.0.6 |
|
#
e827e518 |
| 20-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [llgs] Implement the 'T' packet
Implement the 'T' packet that is used to verify whether the specified thread belongs to the debugged processes.
Sponsored by: The FreeBSD Foundation Different
[lldb] [llgs] Implement the 'T' packet
Implement the 'T' packet that is used to verify whether the specified thread belongs to the debugged processes.
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D128170
show more ...
|
#
630da0e3 |
| 20-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [llgs] Include PID in QC response in multiprocess mode
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D128156
|
#
14d67073 |
| 19-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [llgs] Add a test for multiprocess register read/write
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D128153
|
#
75757c86 |
| 18-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [llgs] Support multiprocess in qfThreadInfo
Update the `qfThreadInfo` handler to report threads of all debugged processes and include PIDs when in multiprocess mode.
Sponsored by: The FreeBS
[lldb] [llgs] Support multiprocess in qfThreadInfo
Update the `qfThreadInfo` handler to report threads of all debugged processes and include PIDs when in multiprocess mode.
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D128152
show more ...
|
#
0481d8ef |
| 18-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [llgs] Add a test for multiprocess memory read/write
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D128150
|
#
a3422793 |
| 15-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [llgs] Support resuming one process with PID!=current via vCont
Extend vCont function to support resuming a process with an arbitrary PID, that could be different than the one selected via Hc
[lldb] [llgs] Support resuming one process with PID!=current via vCont
Extend vCont function to support resuming a process with an arbitrary PID, that could be different than the one selected via Hc (or no process at all may be selected). Resuming more than one process simultaneously is not supported yet.
Remove the ReadTid() method that was only used by Handle_vCont(), and furthermore it was wrongly using m_current_process rather than m_continue_process.
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D127862
show more ...
|
#
3266b117 |
| 14-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [llgs] Add test for resuming via c in multiprocess scenarios
Add a test verifying that it is possible to resume a single process via the `c` packet when multiple processes are being debugged.
[lldb] [llgs] Add test for resuming via c in multiprocess scenarios
Add a test verifying that it is possible to resume a single process via the `c` packet when multiple processes are being debugged. This includes a tiny change to the test program — when `fork()` is called, the child process is no longer terminated immediately but continues performing the same tasks as queued for the parent.
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D127755
show more ...
|
#
c18784ba |
| 12-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [llgs] Implement the vKill packet
Implement the support for the vKill packet. This is the modern packet used by the GDB Remote Serial Protocol to kill one of the debugged processes. Unlike
[lldb] [llgs] Implement the vKill packet
Implement the support for the vKill packet. This is the modern packet used by the GDB Remote Serial Protocol to kill one of the debugged processes. Unlike the `k` packet, it has well-defined semantics.
The `vKill` packet takes the PID of the process to kill, and always replies with an `OK` reply (rather than the exit status, as LLGS does for `k` packets at the moment). Additionally, unlike the `k` packet it does not cause the connection to be terminated once the last process is killed — the client needs to close it explicitly.
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D127667
show more ...
|
Revision tags: llvmorg-14.0.5 |
|
#
e8fe7e93 |
| 10-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [llgs] Make `k` kill all processes, and fix multiple exits
Modify the behavior of the `k` packet to kill all inferiors rather than just the current one. The specification leaves the exact be
[lldb] [llgs] Make `k` kill all processes, and fix multiple exits
Modify the behavior of the `k` packet to kill all inferiors rather than just the current one. The specification leaves the exact behavior of this packet up to the implementation but since vKill is specifically meant to be used to kill a single process, it seems logical to use `k` to provide the alternate function of killing all of them.
Move starting stdio forwarding from the "running" response to the packet handlers that trigger the process to start. This avoids attempting to start it multiple times when multiple processes are killed on Linux which implicitly causes LLGS to receive "started" events for all of them. This is probably also more correct as the ability to send "O" packets is implied by the continue-like command being issued (and therefore the client waiting for responses) rather than the start notification.
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D127500
show more ...
|
#
13eb5b34 |
| 08-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [llgs] Add a test for detach-all packet
Add a test verifying that plain 'D' packet correctly detaches all processes.
Sponsored by: The FreeBSD Foundation Differential Revision: https://revie
[lldb] [llgs] Add a test for detach-all packet
Add a test verifying that plain 'D' packet correctly detaches all processes.
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D127291
show more ...
|
#
313d9c15 |
| 08-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [llgs] Refactor fork/vfork tests, verify state
Refactor the fork and vfork tests to reuse the code better, avoid unnecessary regexps and avoid unnecessary conversions between hex-strings and
[lldb] [llgs] Refactor fork/vfork tests, verify state
Refactor the fork and vfork tests to reuse the code better, avoid unnecessary regexps and avoid unnecessary conversions between hex-strings and integers.
Verify the server state after detaching. In particular, verify that the detached process' PID/TID pair is no longer valid, and that the correct process remains running.
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D127290
show more ...
|
#
d6b3de72 |
| 20-Jun-2022 |
Michał Górny <mgorny@moritz.systems> |
[lldb] [llgs] Fix signo sent with fork/vfork/vforkdone events
Fix ThreadStopInfo struct to include the signal number for all events. Since signo was not included in the details for fork, vfork and v
[lldb] [llgs] Fix signo sent with fork/vfork/vforkdone events
Fix ThreadStopInfo struct to include the signal number for all events. Since signo was not included in the details for fork, vfork and vforkdone stops, the code incidentally referenced the wrong union member, resulting in wrong signo being sent.
Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.llvm.org/D127193
show more ...
|