You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
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.
The text was updated successfully, but these errors were encountered:
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
/opt/bindiff/bin/bindiff --export directory/containing/envoy-binary/
.BinExport
file is createdExpected 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):
.deb
from release pageAdditional 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.The text was updated successfully, but these errors were encountered: