In my LLDB session, memory read 0x00000003 throws an error message.

IMHO, the message error: memory read failed for 0x0 should end with 0x3.

In case this is no bug but intended behaviour, could anybody explain where the offset/trim comes from?

Further details: x86_64

CodePudding user response：

The memory address will be floored (rounded down) to the nearest multiple of 256 (0x100).

CodePudding user response：

If I remember correctly $eax is defined as 0x0, so it's saying that memory read can't read the value inside 0x0.