Does the Toolchain Origin Works for Windows PE file in Linux?

[mali-arf]

I ran Origin tool on PE files and it created empty idioms and instances files with an error stating that "cannot find the file specified 'exe.range' file
and executing "extractFeat" only results in "malloc Assertion"

How can I use this tool for predicting compiler of Windows PE files?
Thank you

[mxz297]

Unfortunately, I have not tested either Dyninst or the toolchain origin tool with PE binaries on Linux or Windows.

[mali-arf]

Thanks for replying Meng. Do you have any idea, where can I get the help from?
I am building DynInst 10.2 on Windows 10 in MSys2 64bit environment. The CMake with generator MinGW went successful after installing boost 1.61 and tbb on MSys and also resolving the cmake CMP0004 policy error by removing a trailing space in the file boost.cmake (line#236).
But Now in make install I am having error that says, conflicting declaration of int _snprintf in msys64_2/mingw64/x86_64-w64-mingw32/include/stdio.h. I comment one the declarations but the error is still there. I dont know how to go about it, next.
Any ideas are welcome.
Many Thanks

[mxz297]

As far as I can tell, there is no human resource in the Dyninst team that is assigned to get Dyninst working on Windows or working with PE binaries. Unfortunately, I don't think this will change in the near future unless additional resource becomes available.

[n738cu]

Xiaozhu is correct.  None of our funding sources is currently interested in supporting Windows.  And Windows is quite different from Linux and other UNIX variants. If someone out there want to take on this task or wants to provide funding for this task, I'd be happy to talk.

…

--bart

On 1/4/2021 11:26 AM, Xiaozhu Meng wrote: As far as I can tell, there is no human resource in the Dyninst team that is assigned to get Dyninst working on Windows or working with PE binaries. Unfortunately, I don't think this will change in the near future unless additional resource becomes available. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AESJYW74T3ORA6TBFBIXYMTSYH25FANCNFSM4VNDYHBA>.