Problems with viewing data in the cpp demo about vscode-debug-visualizer HOT 16 OPEN

I faced the same issue but later I came to know about the solution from here. Print setting in gdb

If GDB is printing a large array, it stops printing after it has printed the number of elements set by the set print elements command and appends ... at the end. This limit also applies to the display of strings. When GDB starts, this limit is set to 200. Setting number-of-elements to unlimited or zero means that the number of elements to print is unlimited.

So what you need to do is that while debugging, execute the command -exec set print elements 0 in debug console.

from vscode-debug-visualizer.

Hi there! Thanks for opening an issue.

Basically, it should work like that. But your debugger (cppdbg) is behaving strange.

When evaluating myGraphJson it only prints { ... }. My extension cannot do much with that.
The debugger does not seem to understand strings. My extension cannot help you if even the debugger does not understand strings.
Maybe you can figure out how to teach the debugger about strings.

from vscode-debug-visualizer.

what debbuger do you recommend to use?
this is my launch file:

from vscode-debug-visualizer.

Sorry, I don't have experience in C++. But I know that in order to debug rust properly, you need to install some formatters for gdb. Maybe someone else with more experience can help?

from vscode-debug-visualizer.

how does the parsing to JSON file works?

from vscode-debug-visualizer.

It pretty much does this:

And parses the result. Clearly {...} is not a json. If you make your debugger to output your string in the debug console when evaluating myGraphJson, my extension will work.

from vscode-debug-visualizer.

The problem is that string is defined as a class in cpp, so to get the data of the string you need to write:
string.data()
but the still there is another problem, because .data() returns an array of char and keeps the \ every time a " is needed in the .json syntax, So the praser can't read the information.

from vscode-debug-visualizer.

The escaping is not the problem, the extension already tries to double unescape it. However, the leading address is a problem.

Do you have an idea how to fix this in a generic way?

from vscode-debug-visualizer.

why the leading address is a problem?

from vscode-debug-visualizer.

Is this 0xf...b8 "{ \"kind\": the start of escaped json?
"{ \"kind\": would be!

from vscode-debug-visualizer.

Do you have any solution?

from vscode-debug-visualizer.

I think that command can even be automatically run through a setup command!
Thanks for finding it!

from vscode-debug-visualizer.

I faced the same issue but later I came to know about the solution from here. Print setting in gdb

If GDB is printing a large array, it stops printing after it has printed the number of elements set by the set print elements command and appends ... at the end. This limit also applies to the display of strings. When GDB starts, this limit is set to 200. Setting number-of-elements to unlimited or zero means that the number of elements to print is unlimited.

So what you need to do is that while debugging, execute the command -exec set print elements 0 in debug console.

hey. I used this method, but without success

from vscode-debug-visualizer.

@zqchinaone can you enter the visualized expr into debug console and post a Screenshot?

from vscode-debug-visualizer.

Is it？

from vscode-debug-visualizer.

It looks like gdb does not recognize the string.

from vscode-debug-visualizer.