Closed GoogleCodeExporter closed 8 years ago
Thank you, will work on it soon.
PS: woah, it's already accepted!
Original comment by feykomylce
on 20 Mar 2015 at 1:53
I fixed the paths, but I found something that doesn't look right. Enabling
hooking creates hook.txt that only contains "MEMORY ACCESS LOGGING STARTED
MEMORY ACCESS LOGGING STOPPED", but enabling it along with trace puts all the
RAM hooks in the trace file along with traced code. Is hook.txt really
seriously intended to only contain those 2 meaningless lines, all the hook log
going to trace file?
Original comment by feykomylce
on 27 Mar 2015 at 3:43
This issue was closed by revision r352.
Original comment by feykomylce
on 27 Mar 2015 at 3:49
Given the question asked in #2, can I ask which way you decided to fix the
issue? Did you redirect the hook output to just the hook file, or both the
hook and trace file? Or something else?
Thanks
Original comment by mcapew...@gmail.com
on 27 Mar 2015 at 4:41
I only fixed what you reported, the thing my subfolder addition broke. But I
don't know if posting hook logs to trace is intended, however it's how it was
in the release. Hence I didn't touch it, I visualize a separate commit handling
these once we come up with the solution. But from looking at how it was coded,
I don't even understand the logic.
Original comment by feykomylce
on 27 Mar 2015 at 5:41
Original issue reported on code.google.com by
mcapew...@gmail.com
on 20 Mar 2015 at 3:30