On a guest VM: > # cat /sys/module/dm_crypt/sections/{.text,.data} > 0xffffffffa049f000 > 0xffffffffa04a4000 Debugger: > (gdb) add-symbol-file drivers/md/dm-crypt.ko 0xffffffffa049f000 -s .data 0xffffffffa04a4000 > add symbol table from file "drivers/md/dm-crypt.ko" at > .text_addr = 0xffffffffa049f000 > .data_addr = 0xffffffffa04a4000 > (y or n) y > Reading symbols from drivers/md/dm-crypt.ko...done. > (gdb) p crypt_target.version > $1 = {1, 15, 0} > (gdb) info addr crypt_target > Symbol "crypt_target" is static storage at address 0xffffffffa04a4020. > (gdb) info addr dm_crypt_exit > Symbol "dm_crypt_exit" is a function at address 0x4e. > (gdb) b dm_crypt_exit > Cannot access memory at address 0x4e
Ping.. This can be repro-ed reliably using gdb-8 and any 4.10 series kernel.