What makes you think that 0x00000000004004 is memory address oc c That address looks more like memory address of assembly code and 0x85f445c7 represents the hexa representation of machine code. The default for addr is usually just after the last address examined—but several other commands also set the default address Info breakpoints (to the address of the last breakpoint listed), info line (to the starting address of a line), and print (if you use it to display a value from memory). This page explains the x command The x command displays the memory contents at a given address using the specified format.
Gdb prints memory addresses showing the location of stack traces, structure values, pointer values, breakpoints, and so forth, even when it also displays the contents of those addresses. Fortunately, gdb provides another command for examining the contents of memory directly—that is, the actual bit patterns In order to use this command, we need to determine the actual memory addresses where the anint and afloat variables are stored. Print the value at a memory address X/d address will print the value as an integer X/i address as an instruction
Is this the correct way to read the value of an address in gdb I was kind of expecting to find a more ascii friendly hex value I am interested in finding the stored string value that is compared against Also do you have a favorite gui tool that you like to use for this type of debugging I have been thinking about trying ddd.
OPEN
