radareorg/radare2

Support bitfields in `pf` and `t` commands

Open

#12,555 opened on Dec 24, 2018

View on GitHub
 (9 comments) (0 reactions) (0 assignees)C (3,229 forks)batch import
commandenhancementgood first issueinputpftypes

Repository metrics

Stars
 (23,826 stars)
PR merge metrics
 (Avg merge 16h 24m) (99 merged PRs in 30d)

Description

See http://mjfrazer.org/mjfrazer/bitfields on how to unpack on different endians.

[0x000068c0]> "td struct qwe { int a:4; int b:16; int c:3; };"
[0x000068c0]> ts
qwe
[0x000068c0]> ts qwe
pf ddd a b c
[0x000068c0]> px 4
- offset -   0 1  2 3  4 5  6 7  8 9  A B  C D  E F  0123456789ABCDEF
0x000068c0  f30f 1efa                                ....
[0x000068c0]> tp qwe
 a : 0x000068c0 = 4196274163
 b : 0x000068c4 = 2303323441
 c : 0x000068c8 = 2303221457

Contributor guide

Research direction
Study the bitfield documentation at the provided URL, and examine the current implementations of the `pf` and `t` commands in radare2 to understand how they parse and display structure fields. Identify where bitfield handling is missing and implement the necessary logic to support bitfields, including correct endian aware unpacking, and update the command parsers and display functions accordingly.
Tech stack
c
Domain
clibackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Cradare2 internalsbitfields
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60