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

Small fixes for RISC-V #2172

Merged
merged 3 commits into from
May 22, 2024
Merged

Conversation

Ordoviz
Copy link
Contributor

@Ordoviz Ordoviz commented May 18, 2024

No description provided.

@Ordoviz Ordoviz force-pushed the various-fixes-for-nonX64-archs branch 3 times, most recently from 3f92b9a to 9b1c194 Compare May 18, 2024 21:37
Copy link

codecov bot commented May 18, 2024

Codecov Report

Attention: Patch coverage is 96.00000% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 58.77%. Comparing base (5e77036) to head (9b1c194).
Report is 13 commits behind head on dev.

Current head 9b1c194 differs from pull request most recent head d756557

Please upload reports for the commit d756557 to get more accurate results.

Files Patch % Lines
pwndbg/disasm/riscv.py 0.00% 4 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             dev    #2172       +/-   ##
==========================================
+ Coverage   3.65%   58.77%   +55.11%     
==========================================
  Files        196      196               
  Lines      25383    25725      +342     
  Branches    2597     2619       +22     
==========================================
+ Hits         928    15120    +14192     
+ Misses     24327     9781    -14546     
- Partials     128      824      +696     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Ordoviz Ordoviz force-pushed the various-fixes-for-nonX64-archs branch from 9b1c194 to 98fba55 Compare May 18, 2024 22:06
@disconnect3d
Copy link
Member

@Ordoviz hmm a recent commit made conflicts here. Can you resolve them?

@OBarronCS Can you help review this?

pwndbg-git from AUR shows hexadecimal constants in masm syntax
(e.g. 80h) for some reason (as if the option CS_OPT_SYNTAX_MASM was set).
This commit makes syscall name printing work regardless of hex syntax.
When the PC was on this instruction, the pwndbg context would not be
printed due to this AssertionError.
According to the specification, "C.JALR expands to jalr x1, 0(rs1)".
@Ordoviz Ordoviz force-pushed the various-fixes-for-nonX64-archs branch from 98fba55 to d756557 Compare May 22, 2024 12:00
@Ordoviz
Copy link
Contributor Author

Ordoviz commented May 22, 2024

I fixed the conflict with #2177. I also removed a commit that adds syscall constants in light of #2175.

@disconnect3d disconnect3d merged commit 2b9beef into pwndbg:dev May 22, 2024
13 checks passed
@disconnect3d
Copy link
Member

Actually, lgtm, merged. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants