-
Notifications
You must be signed in to change notification settings - Fork 116
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
Missing quotation for variables with spaces leads to "Could not expand variable: Variable object not found" #278
Comments
martin-fleck-at
added a commit
to martin-fleck-at/code-debug
that referenced
this issue
Jul 26, 2021
martin-fleck-at
added a commit
to martin-fleck-at/code-debug
that referenced
this issue
Jul 29, 2021
martin-fleck-at
added a commit
to martin-fleck-at/code-debug
that referenced
this issue
Jul 29, 2021
martin-fleck-at
added a commit
to martin-fleck-at/code-debug
that referenced
this issue
Jul 29, 2021
martin-fleck-at
added a commit
to martin-fleck-at/code-debug
that referenced
this issue
Jul 29, 2021
WebFreak001
pushed a commit
that referenced
this issue
Jul 30, 2021
218d824 should have fixed this, so I assume it can be closed. If there is still an issue please report and we'll reopen. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In my program I have a vector variable of a certain type, e.g.,
cl::Platform
. When I list all children using GDB with the M2 interface, the name of that variable is reported asvar_1_platforms::_Vector_base<cl::Platform, std::allocator<cl::Platform> >
(note the spaces in the name). But when I try to get the children of that variable (var-list-children --all-values <name>
) I receive aCould not expand variable: Variable object not found
exception. I traced the issue to the spaces in the variable name as they break the parsing of the name. This can be easily reproduced on the command line.Quoting the variable name fixes the issue for me and I noticed that there are already quotation marks around some other commands in the MI2 class, e.g., around expression when we create a variable. I will push a PR adding those quotation marks shortly.
The text was updated successfully, but these errors were encountered: