| commit | 8167934480a7b6a8e122aa6233aa8ed2e2683d6a | |
| author | David Spickett <david.spickett@linaro.org> | |
| Mon, 27 Nov 2023 09:10:39 +0000 (27 09:10 +0000) | ||
| committer | GitHub <noreply@github.com> | |
| Mon, 27 Nov 2023 09:10:39 +0000 (27 09:10 +0000) | ||
| tree | db77e45abb582f1de9be360fd27ace0eb4097f5d | treesnapshot (tar.gz zip) |
| parent | d045e23c2d00a445e40a8c97471df023d8364f59 | commitdiff |
[lldb] Improve error message for script commands when there's no interpreter (#73321)
It was:
```
error: there is no embedded script interpreter in this mode.
```
1. What does "mode" mean?
2. It implies there might be an embedded script interpreter for some
other "mode", whatever that would be.
So I'm simplifying it and noting the most common reason for this which
is that lldb wasn't built with a scripting language enabled in the first
place.
There are other tips for dealing with this, but I'm not sure this
message is the best place for them.
It was:
```
error: there is no embedded script interpreter in this mode.
```
1. What does "mode" mean?
2. It implies there might be an embedded script interpreter for some
other "mode", whatever that would be.
So I'm simplifying it and noting the most common reason for this which
is that lldb wasn't built with a scripting language enabled in the first
place.
There are other tips for dealing with this, but I'm not sure this
message is the best place for them.
| lldb/source/Plugins/ScriptInterpreter/None/ScriptInterpreterNone.cpp | diffblobblamehistory |