-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Add pyc plugin #16771
Add pyc plugin #16771
Conversation
This pull request introduces 5 alerts when merging e0fc42464f070c12623105e076c59736138541c7 into e9152db - view on LGTM.com new alerts:
|
This pull request introduces 5 alerts when merging ba4e685af6a9a5de7c2fff8f3df0217a965ebc58 into e9152db - view on LGTM.com new alerts:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The bignum impl should be generic and live in r_util. Use size_t for loop variables. Add some tests
Regarding the bignum in r_util - it was discussed long time ago for supporting long registers such as SSE, AVX, etc: https://github.com/radareorg/radare2/issues/6093#issuecomment-312997305 |
This pull request introduces 5 alerts when merging 22bdd557276ba4c16896b74b0935c26c1a49a47b into 4fa630c - view on LGTM.com new alerts:
|
This pull request introduces 5 alerts when merging 52c59159f1035309642291418d93b6c8750e63de into 64e6df5 - view on LGTM.com new alerts:
|
This pull request introduces 5 alerts when merging 19dfafd753925f5ba9401177fd8f4590f2f56276 into 03a5c4d - view on LGTM.com new alerts:
|
As it's been said above, it would be great if you could add some unit tests for libr/util/big.c :) |
@xarkes It's still working in progress. I will mention |
Then i would suggest to use R_IPI
… On 6 May 2020, at 06:38, FXTi ***@***.***> wrote:
@FXTi commented on this pull request.
In libr/asm/arch/pyc/opcode.c:
> + { "v3.8.0a2", opcode_38 },
+ { "v3.8.0a3", opcode_38 },
+ { "v3.8.0a4", opcode_38 },
+ { "v3.8.0b1", opcode_38 },
+ { "v3.8.0b2", opcode_38 },
+ { "v3.8.0b3", opcode_38 },
+ { "v3.8.0b4", opcode_38 },
+ { "v3.8.0rc1", opcode_38 },
+ { "v3.8.1", opcode_38 },
+ { "v3.8.1rc1", opcode_38 },
+ { "v3.9.0a1", opcode_39 },
+ { "v3.9.0a2", opcode_39 },
+ { "v3.9.0a3", opcode_39 },
+};
+
+bool pyc_opcodes_equal (pyc_opcodes *op, const char *version) {
No, it will be used outside the file
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
This pull request introduces 8 alerts when merging 379b51c80c6f0a57f5fe70e24c54ac0c00b1deb5 into 4700810 - view on LGTM.com new alerts:
|
By the way, in the future I recommend to squash this PR in two commits - one adding the new bignum + tests, and another - the pyc plugin itself. |
This pull request introduces 8 alerts when merging 7dfb6cb991a4232aa3694c1128a3b88eb9a7fac6 into 2a4cc15 - view on LGTM.com new alerts:
|
Actually, I would suggest to create two completely different PRs. One for RBig and one for PYC. They are very different things and pretty big on their own, so I would prefer to review/merge first the RBig one and then the PYC. WDYT? |
Agree with ret2libc
… On 8 May 2020, at 11:19, Riccardo Schirone ***@***.***> wrote:
Actually, I would suggest to create two completely different PRs. One for RBig and one for PYC. They are very different things and pretty big on their own, so I would prefer to review/merge first the RBig one and then the PYC. WDYT?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Agree with ret2libc. But can we squash this into two commits? like @XVilka said. |
This pull request introduces 9 alerts when merging 0bc7513b86f968109b4aaa013ed51f7f52eab359 into 72f9795 - view on LGTM.com new alerts:
|
Fix the lgtm issues and lgtm |
You removed dependence, but BN changes are still here. Could you please drop them? |
This pull request introduces 1 alert when merging 446824b into 9f2a98b - view on LGTM.com new alerts:
|
I went ahead and merged it. Please send future improvements in a separate PR. This one got too long. |
Detailed description
Move RBin, RAsm & RAnal plugins for python bytecode from https://github.com/radareorg/radare2-extras
.arch
field pass in RBinlibr/anal/p/anal_rsp.c
Test plan
test pass
Closing issues
radareorg/radare2-extras#244