Skip to content
This repository has been archived by the owner on Aug 13, 2024. It is now read-only.

"Mark as decompiled" not synced. #68

Open
parazyd opened this issue Mar 13, 2021 · 1 comment
Open

"Mark as decompiled" not synced. #68

parazyd opened this issue Mar 13, 2021 · 1 comment
Labels
non-propagated feature Features of IDA that are not propagated over IDArling but do not risk corrupting the IDB

Comments

@parazyd
Copy link

parazyd commented Mar 13, 2021

Hi. It seems that when marking a function as decompiled in IDA, it does not get synced with other IDArling users.

Is this intended or something that can be implemented/fixed?

@saidelike
Copy link
Collaborator

Hi parazyd,

The short answer is: it is not intended, and it may be possible to add it.

If you want to understand why certain events are synced vs other not-synced, I advise you read the documentation: https://github.com/fidgetingbits/IDArling#features

The hooks defined in https://github.com/fidgetingbits/IDArling/blob/master/idarling/core/hooks.py#L60 actually dictate what is synced already.

If you want to add support for it, you have to check what event is generated by IDA itself when you click "Mark as decompiled" then add a hook for this particular event in IDArling.

Let me know if you have any question.

@saidelike saidelike added the non-propagated feature Features of IDA that are not propagated over IDArling but do not risk corrupting the IDB label Mar 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
non-propagated feature Features of IDA that are not propagated over IDArling but do not risk corrupting the IDB
Projects
None yet
Development

No branches or pull requests

2 participants