c++ - Linux gdb 'examine' behavior -


i'm using gdb explore core file on linux , noticed weird behavior when examining memory addresses:

(gdb) x/f 0xbd091a10 0xbd091a10:     0 (gdb) x/g 0xbd091a10 0xbd091a10:     65574 (gdb) x/f 0xbd091a10 0xbd091a10:     65574 

these statements run directly back, , don't understand why examining float returns inconsistent results. value 65574 make sense corresponds identity of last loaded item process.

does know reason this?

version details:

linux mx534vm 2.6.18-308.el5 #1 smp fri jan 27 17:17:51 est 2012 x86_64 x86_64 x86_64 gnu/linux

gnu gdb (gdb) red hat enterprise linux (7.0.1-32.el5)

there no inconsistency in this. 'f' , 'g' specifiers in different categories, 'f' format , 'g' unit size. each specifier, when used, becomes default own category holds subsequent uses of 'x'. thus, 2 last commands both equivalent x/fg 0xbd091a10.


Comments

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

Python ctypes access violation with const pointer arguments -