Debugger doesn't show correct information for array initialized with runtime length

[YXuewei]

I ran into a problem that if I declare an array with know length such as
int array[5];
the debug works perfectly, however, if I initialize an array with length only know at run time for example
int n = someinput; int array[n]
the debug doesn't show correct information for this array, it shows length of 0, and can't inspect the element. Please see pic below

I'm absolutely, completely, definitely sure image[] and input[] by the time is already initialized correctly.

[pieandcakes]

@YXuewei What OS are you running on and if you are using gdb, do you have gdb's pretty-printing enabled?

[YXuewei]

@pieandcakes I'm using windows, and I do turned pretty-printing on. I write a sample code to demonstrate what it looks like.


The First one is my lauch.jason setting. I use gdb-pyrhon27.exe so that I can use pretty-pritting. And the second pic is what it is like when I inspect values. Form debugger console you can see that I use command -exec -enable-pretty-printing to enable pretty-printing and it shows it have been done.

[pieandcakes]

@YXuewei The visualization of the variables through pretty printing is provided by gdb's community. If you want, you can search and see if there is another option to help visualize the array. We also support .natvis visualization using a .natvis visualizer file but you would also need to create one from scratch. It seems like gdb is returning different information for each case, which we have no control over.

[YXuewei]

@pieandcakes Is that possible to let VSCode to use GDB in WSL? If it is what we going to have in Windows Creator update I will save me sometime for getting a *nix or some money on macOS.

[YXuewei]

@pieandcakes It is the same if I use LLDB, see screen shoots below. I tried this with a MacBook Pro.

[pieandcakes]

@YXuewei We also enabled python formatting for lldb recently. I don't know if the behavior is the same. You can enable "logging": { "engineLogging": true } and see what we send gdb/lldb and what we get back. I suspect we are getting different data back for each case.

[YXuewei]

@pieandcakes No it doesn't work, it didn't bring any difference without the command when inspecting. It should be a way in LLDB to enable something like pretty printing in GDB. There is no reason that gdb can do it but LLDB can not. Otherwise how does Xcode be able to view object contains or dynamic array?

[pieandcakes]

@YXuewei Unfortunately LLDB the pretty printing is compiled in and not able to be disabled. I don't know if Xcode provides additional pretty printing configurations but you can look at the documentation here: http://lldb.llvm.org/varformats.html

The ones included in our package are located at:
~/.vscode/extensions/ms-vscode.cpptools-0.10.5/debugAdapters\lldb\lib\python2.7\site-packages\lldb\formatters

[WardenGnaw]

Closing issue with no recent updates.

If this issue is still occuring, please open a new issue.