DDD(debugger) graphic display format
When I give for example graph display B[576] @576, I can see the array values, 576 values from array B[576]. But I can't understand the display result seen below. What does the first element 0 <225x> mean? Does it mean 225 zero values?
Solution
Yes, its showing that the value is repeated 225 times.
Using GDB, an array value that is repeated 10 or more times is displayed only once. The value is shown with a postfix added, where n is the number of times the value is repeated. Thus, the display 0x0 <30x> stands for 30 array elements, each with the value 0x0. This saves a lot of display space, especially with homogeneous arrays. (source)
- GDB grep info sources files
- LLDB how to add symbol files at certain address?
- Running a program with segmentation fault works well with gdb
- Why am I unable to copy and execute a function in C?
- GDB debugger terminates after using step over
- Eclipse/MinGW/CDT/GDB and problems with debugging
- How can I disable new thread/thread exited messages in gdb?
- How i can static build GDB from source?
- Problems adding a breakpoint with commands from command line with ex command
- Is there a C++ gdb GUI for Linux?
- How to skip a number of iterations of a loop in GDB?
- How to install GCC and GDB for WSL(windows subsytem for linux)?
- GDB keeps downloading debug info
- GDB error when reading an std::string variable
- Crashes normally, but not with GDB
- gdb not found when setting up Mingw-64w in VSCode
- How to solve GDB unexpected demangled name?
- GDB does not attempt to load any shared library when core file is loaded
- GDB hangs after continuing from "start_kernel" breakpoint?
- Debugging FFMPEG Code (libavformat files breakpoint)
- In gdb can I save or pass values like the symbol-filename for later use?
- gdb - have output of custom script be displayed after each command
- Arm64 Assembly: How to properly manage frame pointer?
- How to add breakpoint when thread sanitizer reports data-race?
- thread-aware gdb for the Linux kernel
- Objective-C: variable optimized away by compiler
- how to prevent some values from being optimized out in linux kernel debugging?
- Using gdb to convert addresses to lines
- Is there a quick way to display the source code at a breakpoint in gdb?
- Why GDB jumps unpredictably between lines and prints variables as "<value optimized out>"?