Skip to content

MemoryRegion possibly wrong on Windows #5

@holly-hacker

Description

@holly-hacker

According to @Azukee, memory scanning on Windows is broken.

[1:01 PM] HoLLy: also what about the error you had yesterday?
[1:01 PM] HoLLy: with the memory regions starting at 0
[1:02 PM] Snowy: well in the scan you had var region
[1:02 PM] Snowy: since i think MemoryRegion is an interface
[1:02 PM] HoLLy: yea
[1:02 PM] Snowy: I just changed it to WindowsMemoryRegion and used BaseAddress and RegionStart
[1:02 PM] Snowy: and not Start and End
[1:02 PM] Snowy: so not really a fix
[1:02 PM] Snowy: but this is windows only so i just botched something together
[1:02 PM] HoLLy: oh so I didn't implement windowsmemoryregion properly then

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinggood first issueGood for newcomers

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions