cgdb
why does gdb increment memory addresses in units of 10
I'm trying to understand why gdb shows memory addresses in increments of 10[hex].
I have compiled my c program with -m32 -z execstack -fno-stack-protector flags and turned of ASLR.
When I debug my program, it shows me the following
When I attempt to query the next address it appears to cycle through the bytes
I'm having trouble understanding this behavior of gdb.
Furthermore, if I create a char buf[n] size of n in my c program I can't accurately count the space used by buf while debugging, I'm wondering how the cycling effect plays into this as well.
Solution
I think your are confused by little-endian (of 32-bit integers):
In memory the first 8 bytes are
0x54ffffc5 -> c5 ff ff 54
0x54ffffc5 -> c5 ff ff 54
so if you step one byte in memory you will find
<skip first byte> ff ff 54 c5 ff ff 54 ...
so you see (as 32-bit integer)
ff ff 54 c5 -> 0xc554ffff
- Is this declaration UB?
- Calling an external C function (in a shared lib) from Perl with Inline/C does not work
- Eclipse C/C++ how to find variable belongs to which struct quickly
- Is this truly best way to delete last element in C?
- Why do we need address virtualization in an operating system?
- Can a real floating-point type alias a complex floating-point type in C?
- Shadowing an iterator inside a for loop has undefined (?) behaviour in C
- Can a C program execute successfully if main() is defined as a macro?
- Ambiguity in scope of for loop declaration versus body
- Understanding the difference in timing of two functions that increment each element of an integer array
- Why MSVC generates warning C4127 when constant is used in "while" - C
- Executing a user-space function from the kernel space
- Why must the variable used to hold getchar's return value be declared as int?
- mpirun -np 4 ./a.out doesn't use all my cores (ubuntu 24.04LTS)
- Sleep for N seconds and wait for keypress
- Dereference twice in gdb
- Is it safe to cast a struct pointer to a different struct pointer having a prefix of elements?
- Can a C compiler legally reject a program if its call stack depth exceeds a fixed limit at compile time?
- return type defaults to 'int' [-Wimplicit-int]
- What is the scope of `fesetround()`?
- Which specific optimization flag causes libm functions to be treated as pure?
- How to render text in SDL2?
- Why would you use 'extern "C++"'?
- Strange Behavior Compiler Ignoring NULL Check Unless I Print Something in the if Statement
- Fast inverse square root using fixed point instead of floating point
- What is the const qualifier attached to in C: the memory area or the pointer?
- GCC options for strictest C code?
- How to do an explicit fall-through in C
- How do compilers treat CONST qualifier when the pointer points to a memory location obtained with malloc()?
- C: cmocka headers - how to unittest?