Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Running bindiff export does not result in `.BinExport` file being created

Abierto
#52 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Área
reverse-engineering, tooling

Línea de trabajo

Comienza con la reproducción usando /opt/bindiff/bin/bindiff --export en el binario de Envoy e inspecciona la ruta de exportación de IDA mencionada en main_plugin.cc. Compara los archivos observados con opensnoop y revisa ~/.bindiff/logs/bindiff_idapro.log; se considera terminado cuando se crea el archivo .BinExport esperado para las versiones indicadas de IDA y Bindiff.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Describe the bug
I'm trying to diff an envoy file containing debug symbols against an optimized release image. I initially tried to diff them against each other through the IDA plugin window and received the "Exporting the secondary database failed." error.

After looking into the source a bit, I tried to run the /opt/bindiff/bin/bindiff directly to isolate what the problem is. It appears that the .BinExport files aren't being created by IDA. Please see my reproduction steps below and let me know if I can provide any more helpful context!

To Reproduce

  1. Download envoy v1.31.1
docker pull envoyproxy/envoy:v1.31-latest
container_sha=$(docker create envoyproxy/envoy:v1.31-latest)
docker cp ${container_sha}:/usr/local/bin/envoy ./
  1. Open binary in IDA and wait for initial analysis to complete
  2. Save IDA database file and close IDA
  3. Run bindiff export from the command line -- /opt/bindiff/bin/bindiff --export directory/containing/envoy-binary/
  4. See that no .BinExport file is created

Expected behavior
That a .BinExport file is created and I'm able to diff a file with debug symbols and the optimized release.

Environment (please complete the following information):

  • OS and version: Ubuntu 22 VM
  • Locale: US English
  • Disassembler and version: IDA Free 8.4
  • Bindiff v8 -- installed .deb from release page

Additional context

I noticed that bindiff is running the following ida64 command. I tried running that directly on my machine and used opensnoop to track what files ida64 is writing. Attached below are the commands I ran and the output from opensnoop. The ~/.bindiff/logs/bindiff_idapro.log file also doesn't contain much information.

Screen Shot 2024-08-12 at 3 05 21 PM

Lenguaje dominante
Java
Estrellas
3.2k
Forks
240
Sin PR fusionados en 30 d

Preparar el entorno

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 google/bindiff

Todos los issues de google/bindiff

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.