David Spickett
bb01fd57bc
[lldb] Require paused process and frame for "register info" command ( #67124 ) ...
Prior to this the command would simply crash when run on a running
process.
Of the three register commands, "info" was the only one missing these
requirements. On some level it makes sense because you're not going to
read a value or modify anything, but practically I think lldb assumes
any time you're going to access register related stuff, the process
should be paused.
I noticed this debugging with a remote gdb stub, so I've recreated that
scenario using attach in a new test case.
2023-09-22 15:55:27 +01:00
2023-03-21 16:24:36 -07:00
2023-07-06 16:19:19 -07:00
2023-06-06 10:58:34 -07:00
2023-01-10 11:47:43 +01:00
2023-06-06 10:58:34 -07:00
2023-01-10 11:47:43 +01:00
2022-10-31 14:40:41 -07:00
2023-01-10 11:47:43 +01:00
2022-07-12 16:23:03 -07:00
2023-08-02 15:33:32 -07:00
2023-03-06 10:42:32 -08:00
2023-05-18 09:44:11 -07:00
2023-05-18 09:44:11 -07:00
2023-07-19 17:11:21 -04:00
2022-06-27 15:14:41 -07:00
2023-01-10 11:47:43 +01:00
2022-06-17 15:08:02 -07:00
2023-06-26 10:36:41 -07:00
2023-09-01 21:32:24 -07:00
2023-02-13 10:15:52 +00:00
2023-07-10 14:50:40 -07:00
2023-06-29 08:21:42 +00:00
2023-01-13 09:13:03 -08:00
2023-06-06 10:58:34 -07:00
2023-08-21 12:44:17 -07:00
2022-06-27 15:14:41 -07:00
2023-06-06 10:58:34 -07:00
2023-02-09 19:35:00 -08:00
2023-09-22 15:55:27 +01:00
2023-01-10 11:47:43 +01:00
2022-06-17 15:08:02 -07:00
2023-06-06 10:58:34 -07:00
2023-06-06 10:58:34 -07:00
2023-07-03 14:12:39 -07:00
2023-01-10 11:47:43 +01:00
2023-09-11 11:00:57 +00:00
2023-07-06 16:19:19 -07:00
2022-06-28 17:54:30 -07:00
2022-06-28 17:54:30 -07:00
2023-06-06 10:58:34 -07:00
2023-08-30 14:14:28 -04:00
2022-06-27 15:14:41 -07:00
2023-09-21 14:50:34 -07:00
2023-02-28 11:39:58 -08:00
2022-07-14 21:18:07 -07:00
2023-03-23 14:05:06 -07:00
2023-03-03 19:33:02 -08:00
2023-01-10 11:47:43 +01:00
2022-01-23 11:07:14 -08:00
2023-06-06 10:58:34 -07:00
2022-07-14 21:18:07 -07:00
bb01fd57bc