More conservative field resolution in MLIL/HLIL for bitfields

Evaluación

Este issue todavía no se ha evaluado.

Descripción

What is the feature you'd like to have?
The new bitfield support in structures is awesome, but until bitfield resolution is added to MLIL/HLIL (https://github.com/Vector35/binaryninja-api/issues/7533), I think there should be at least an option to disable displaying bitfield accessors on MLIL/HLIL.

Is your feature request related to a problem?
For example when using the SVD loader plugin, a bunch of registers will include bitfields, and HLIL will always defaults to the first bitfield. This is my opinion produces misleading output and makes you think the code is dealing with a bitfield when it is really not.

Here are two examples:

Are any alternative solutions acceptable?
I see two possible ways:

• Add an option to enable/disable using bitfields in the MLIL/HLIL views
• In the SVD plugin, add an option to not create bitfields in the structures

The second option is not very good as the problem will persist for any structure using bitfields which wasn't created by the SVD plugin.

Additional Information:
One clear example where printing bitfields will be misleading is working with an MCP server. Any LLM accessing the MLIL/HLIL view produced by binary ninja will think that is bitfield being accessed and totally mess up....

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

1. Lee el issue completo y luego la guía de contribución del proyecto.
2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
3. Haz un fork del repositorio y trabaja en una rama.
4. Abre un pull request que haga referencia al número del issue.

Más de Vector35/binaryninja-api

• `Function::IsVariableUserDefinded` is misspelt in the C++ API Abierto

  Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100

  Vector35/binaryninja-api#8540 · Abierto el 10/9/2026

• MSP430: conditional_jump! macro initialises new_true to true, emitting a spurious jump Abierto

  Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100

  Vector35/binaryninja-api#8516 · Abierto el 3/9/2026

• MSP430: Sub lifts operands in reverse order (inconsistent with Cmp) Abierto

  Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100

  Vector35/binaryninja-api#8503 · Abierto el 1/9/2026

• normalize time logs from WARP Abierto

  Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100

  Vector35/binaryninja-api#8446 · Abierto el 20/8/2026

• component data variable notifications raise AttributeError Abierto

  Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100

  Vector35/binaryninja-api#8444 · Abierto el 20/8/2026

Todos los issues de Vector35/binaryninja-api

Issues similares

• RingOutlierFilterComponent never sets row_step on its output PointCloud2 (always 0) Abierto

  Dificultad 1/5 1-3 horas Aptitud para principiantes 92/100

  autowarefoundation/autoware_universe#13413 · Abierto el 21/9/2026

• HTML export opens a span per character for system messages Abierto

  Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100

  Mudlet/Mudlet#10974 · 1 comentario · Abierto el 21/9/2026

• [Memory Safety] Memory Safety Analysis: artifact download blocked by network egress restrictions (run `#92`) Abierto
  automated-analysis bug memory-safety

  Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100

  Z3Prover/z3#10883 · Abierto el 21/9/2026

• Eval bug: SIGSEGV in token-counting routes when the request arrives while the server is sleeping (stale vocab/mctx captured before the wake barrier) Abierto

  Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100

  ggml-org/llama.cpp#29188 · Abierto el 20/9/2026

• Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Abierto

  Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100

  gazebosim/gz-sensors#662 · 1 comentario · Abierto el 20/9/2026

Más issues de C++