Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Name resolution of InitLateStaticFieldStub not done in asm files #89

Open
cryptax opened this issue Jul 29, 2024 · 0 comments
Open

Name resolution of InitLateStaticFieldStub not done in asm files #89

cryptax opened this issue Jul 29, 2024 · 0 comments

Comments

@cryptax
Copy link

cryptax commented Jul 29, 2024

In the ASM directory, I have assembly such as this, which is calling 0x2c0c84.

    //     0x1a634c: ldr             x2, [PP, #0x2378]  ; [pp+0x2378] Field <::.debugPrint>: static late (offset: 0x710)
    //     0x1a6350: bl              #0x2c0c84

Notice that the name corresponding to function at 0x2c0c84 is not provided, although usually, function names are provided by Blutter. An example where it works:

//     0x1a635c: bl              #0x2c2a94  ; AllocateArrayStub

Strangely, Blutter knows that the function at 0x2c0c84 is InitLateStaticFieldStub, because both the IDA script and the Radare2 scripts have the information:

$ grep -r 2c0c84 .
./r2_script/addNames.r2:f method.InitLateStaticFieldStub=0x2c0c84
./ida_script/addNames.py:idaapi.set_name(0x2c0c84, "InitLateStaticFieldStub_2c0c84")
./ida_script/addNames.py:ida_funcs.add_func(0x2c0c84, 0x2c0cc0)
./ida_script/addNames.py:ida_funcs.add_func(0x2c0c1c, 0x2c0c84)
...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant