Christian Blichmann

Hi there! Thanks for your report. A similar issue seems to occur in [b/151242195 ](http://issuetracker.google.com/151242195). See there for more details. TL;DR - this is likely or heuristic for detecting non-returning...

Also happens in IDA 7.4 and BinExport 11. Both BinDiff 5 and 6. Another workaround might be to use the Ghidra exporter (also in this repo or in the release...

> [...] > Sorry, I do not know how to improve the heuristic. But why not let IDA figure out how to deal with non-returning functions? Similar to Ghidra :)...

BinDiff 7 sets `-OBinExportX86NoReturnHeuristic:FALSE` by default. We should still propagate any _"No Return"_ attribute that a disassembler sets.

Hi there, BinDiff uses BinExport's [`GetOrCreateTempDirectory()`](https://github.com/google/binexport/blob/main/util/filesystem.cc#L165) and then invokes the [IdbExporter](https://github.com/google/binexport/blob/main/util/idb_export.h): ```c++ auto temp_dir = GetOrCreateTempDirectory("BinDiff"); // ... const std::string secondary_temp_dir = JoinPath(*temp_dir, "secondary"); // ... const auto& config =...

Did my suggestion to set the `TEMP` environment variable help at all? Another thing to check: Are you using a non-US locale or non US-English settings for the user interface...

(back from vacation) > I still get an error after trying,(i forgot to reply... Does that mean you set `TEMP` to a different value and it didn't help? Also (see...

@SiOuz, what is your language locale? I'm guessing non-US also?

@babrath, what happens if you manually execute the command that is printed (try setting `-OBinExportAlsoLogToStdErr:TRUE`, though)?

No that wasn't an error. It's likely due to the way BinExport is built (internally, we still build with 10.1.3). Ghidra's extension versioning is... not great. They basically treat each...