[DiscordArchive] speaking about the debug mode issue and alike, doesn't your RE tool give you ability to see who writ
[DiscordArchive] speaking about the debug mode issue and alike, doesn't your RE tool give you ability to see who writ
Original source
speaking about the debug mode issue and alike, doesn't your RE tool give you ability to see who writes to the adress?
rektbyfaith
04-17-2021, 04:21 PM #1Archived author: Skarn • Posted: 2021-04-17T16:21:14.409000+00:00
Original source
speaking about the debug mode issue and alike, doesn't your RE tool give you ability to see who writes to the adress?
Original source
the one that is responsibly for enabling those prints
rektbyfaith
04-17-2021, 04:21 PM #2Archived author: Skarn • Posted: 2021-04-17T16:21:25.244000+00:00
Original source
the one that is responsibly for enabling those prints
Original source
Maybe, I haven't done that much reverse engineering of assembly like this. I traced it to a subroutine with 250+ inputs that appears to be loading all the various properties, but didn't know where to take it from there
rektbyfaith
04-17-2021, 04:23 PM #3Archived author: stoneharry • Posted: 2021-04-17T16:23:13.878000+00:00
Original source
Maybe, I haven't done that much reverse engineering of assembly like this. I traced it to a subroutine with 250+ inputs that appears to be loading all the various properties, but didn't know where to take it from there
Original source
why assembly tho if you have pseudocode?
rektbyfaith
04-17-2021, 04:24 PM #4Archived author: Skarn • Posted: 2021-04-17T16:24:39.963000+00:00
Original source
why assembly tho if you have pseudocode?
Original source
The psuedocode isn't that useful when you have v1 through to v250+. You don't know what is at each pointer
rektbyfaith
04-17-2021, 04:25 PM #5Archived author: stoneharry • Posted: 2021-04-17T16:25:06.724000+00:00
Original source
The psuedocode isn't that useful when you have v1 through to v250+. You don't know what is at each pointer
Original source
theoretically you can patch the instruction right before the print
rektbyfaith
04-17-2021, 04:25 PM #6Archived author: Skarn • Posted: 2021-04-17T16:25:34.362000+00:00
Original source
theoretically you can patch the instruction right before the print
Original source
to e.g. check against true all the time
rektbyfaith
04-17-2021, 04:25 PM #7Archived author: Skarn • Posted: 2021-04-17T16:25:44.419000+00:00
Original source
to e.g. check against true all the time
Original source
I was hoping to potentially patch it to initialise debug mode as true rather than false, might be easier than trying to identify what sets that flag. But yeah, couldn't seem to figure it out
rektbyfaith
04-17-2021, 04:26 PM #8Archived author: stoneharry • Posted: 2021-04-17T16:26:15.961000+00:00
Original source
I was hoping to potentially patch it to initialise debug mode as true rather than false, might be easier than trying to identify what sets that flag. But yeah, couldn't seem to figure it out
Original source
the fact that it debug mode is present probably means it is turned on by some launch argument or something
rektbyfaith
04-17-2021, 04:27 PM #9Archived author: Skarn • Posted: 2021-04-17T16:27:08.895000+00:00
Original source
the fact that it debug mode is present probably means it is turned on by some launch argument or something
Original source
normally such things are stripped away on compile time
rektbyfaith
04-17-2021, 04:27 PM #10Archived author: Skarn • Posted: 2021-04-17T16:27:19.444000+00:00
Original source
normally such things are stripped away on compile time
1 Guest(s)
1 Guest(s)