Logging memory with the debugger
|
10-30-2022, 05:40 PM
Post: #4
|
|||
|
|||
RE: Logging memory with the debugger
Sorry, {[a1,4]} would log 4 bytes (32-bits.) You're right, my example of 8 won't work as it doesn't support 64-bit log values.
If it logs nothing, are you sure your breakpoint is being hit? Even without a log format, it will log something, it'll just be generic. You can put words outside the {} to make sure. For example, just yesterday I was logging things using {[[[[a0]+0x78]+0x34]+0x2c]}. -[Unknown] |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
Logging memory with the debugger - kenaku - 10-28-2022, 11:11 PM
RE: Logging memory with the debugger - [Unknown] - 10-29-2022, 01:13 AM
RE: Logging memory with the debugger - kenaku - 10-30-2022, 04:25 PM
RE: Logging memory with the debugger - [Unknown] - 10-30-2022 05:40 PM
RE: Logging memory with the debugger - kenaku - 10-31-2022, 12:03 AM
RE: Logging memory with the debugger - [Unknown] - 11-01-2022, 06:10 AM
|