mirror of
https://github.com/GaloisInc/macaw.git
synced 2024-12-18 11:31:35 +03:00
2092a0fd01
The code pointer discovery in macaw can't handle this case because we never write the code pointers into memory - we only read them. We really need a way to tell macaw about code pointers. The easy workaround is to pull all of the function entry points out of the TOC and just seed the macaw search with them, but it would be nice to be able to identify them from first principles.
12 lines
415 B
Plaintext
12 lines
415 B
Plaintext
R { funcs = [ (0x100001d0, [ (0x100001d0, 84)
|
|
, (0x10000224, 56)
|
|
, (0x10000230, 44)
|
|
, (0x1000025c, 32)
|
|
])
|
|
, (0x10000180, [ (0x10000180, 68)
|
|
])
|
|
, (0x10000148, [ (0x10000148, 44)
|
|
])
|
|
]
|
|
, ignoreBlocks = [0x1000027c]
|
|
} |