Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Commands history and auto completion #784

Open
davxy opened this issue Oct 8, 2022 · 1 comment
Open

Commands history and auto completion #784

davxy opened this issue Oct 8, 2022 · 1 comment
Labels
enhancement Enchancement request

Comments

@davxy
Copy link

davxy commented Oct 8, 2022

When using 'stock' lldb on Linux, in the command prompt I have access to commands history (using up/down arrows) and commands completion (using tab).

Apparently this doesn't work in pre-built codelldb (fetched from Releases).

Is there any workaround (e.g. environment variable to set) to make it work or should I have to recompile the project using some compiler flag?


Furthermore.

Has been a while now that this project is the only fork of lldb capable of print a proper version of enumerations with embedded values (e.g. Option, Result, etc).

Is the any chance to have you guys propose a PR to embed your Rust enums magic within the lldb upstream project? I think that would be super appreciated by a lot of persons

Thank you for your fantastic work


References:

@davxy davxy added the enhancement Enchancement request label Oct 8, 2022
@vadimcn
Copy link
Owner

vadimcn commented Oct 8, 2022

Is there any workaround (e.g. environment variable to set) to make it work or should I have to recompile the project using some compiler flag?

No. The liblldb bundled with CodeLLDB has been intentionally build without line editing support in order to reduce the number of system dependencies (in this case libedit.so). The intended use for it is a debug adapter in VSCode, which provides its own line editing facilities it the command line of the debug console.

Is the any chance to have you guys propose a PR to embed your Rust enums magic within the lldb upstream project?

This had been proposed a few years back, however no one stepped forward to be the maintainer of that code. And after several previous experiences of language support having been added and then removed from LLDB due to lack of maintenance (happened with Go and Java IIRC), LLDB folks were not excited about this proposal.
This will probably still happen, especially if Rust manages to establish as one of the Linux kernel languages, but I can't tell when.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enchancement request
Projects
None yet
Development

No branches or pull requests

2 participants