-
Notifications
You must be signed in to change notification settings - Fork 6.6k
Introduce operand offset (C++ and Java) #4812
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
base: master
Are you sure you want to change the base?
Introduce operand offset (C++ and Java) #4812
Conversation
Did you forget to |
🤔 - I don't have this file (and I don't need it either). The two commits are the two patches I use to build Ghidra 10.1.5. (Update to 10.2.2 is in progress 😉). |
Thanks for the hint. 39baf3a removed ParserWalker. |
46fc999
to
c795bf5
Compare
Rebased to head |
You did not take my comment from 12/12/2022 into account:
|
c795bf5
to
934791e
Compare
Sorry, @jobermayr, indeed Fixed now. |
934791e
to
f34684b
Compare
Fix (edit: previously it was to generated pcodeparse.cc):
|
Signed-off-by: Klaus Kämpf <[email protected]>
Signed-off-by: Klaus Kämpf <[email protected]>
f34684b
to
607ae4a
Compare
Thanks @jobermayr - I had fixed this in the generated file only 🤦🏻 Can you point me to your build system ? It seems as if you've extended "make realclean" within |
Not really. I only created a makeBison.sh to quickly regenerate files after modifications to On ghidra-staging I try to keep all pull requests (and their updates) building. |
To apply and build after 8fbd171 / ae6f7b4: https://github.com/jobermayr/ghidra-staging/blob/master/4812-Introduce-operand-offset-C-and-Java.patch |
I'd assume these commits are included in Ghidra_11.0.2_build ?! 🤔
It looks wrong to me. For example:
I carry my commits along at my own fork, currently at (resp. on top of) Ghidra_11.0.2_build. See https://build.opensuse.org/package/show/security:forensics/ghidra for the patches. |
No. master which leads currently to 11.1
I try to collapse it like ae6f7b4: |
I will need to take a closer look. Not sure I can manage it this week. Asking for your patience 😉 |
I usually rebase my branch only on major releases. |
This PR introduces a new pre-defined symbol named
operand_offset
to expose the relative byte offset of the current operand frominst_start
. This is required to correctly compute PC-relative operand addresses for DEC VAX.See #4606 about my attempts of solving this (and failing) with existing methods.
While the diff looks relatively large, there's no new computation going on. It merely exposes the offset which
parserWalker
already has. The rest of the code is just "symbol ceremony" copied frominst_start
.There are two commits, the first one covers the "C++" side, the second covers the "Java" side.
Fixes #4606