Custom Query (80 matches)

There is one incompatibility with GCC 4.7.3 in Odin: the PE and PEC tools.

They use custom startup code (to reserve as low virtual address in private memory space as possible — this is vital for some WIn32 .EXE files which have the very low virtual entry point which we must be able to provide as there is 1-to-1 address mapping).

However, GCC 4.7.3 puts a reference to __ehInit (C++ exception handling) in each object file it generates. And since we don't link to the normal CRT startup code in case of PE/PEC, this symbol remains undefined. This seems like a bug of GCC, more details are here: ​https://github.com/psmedley/gcc/issues/8.

installed rpm/yum onto a clean machine, followed by libodin and odin-doc. However, none of the .exe files were included, requiring them to be extracted from the zip file.

The file flash.txt for 0.4.1 GA states:

• Registry:

This release of the Flash Plugin Wrapper no longer uses the registry to find it's location. You can check with regedit2.exe if the key "Flash10_plugin" exists, but it should be removed by the installer.

At the suggestion of Steven Levine, this could be made clearer, that the registry referred to is the OS/2 profile registry OS2.INI . I assume that the Open32 registry USER.DAT is still in use.

Suggested change:

• Registry:

This release of the Flash Plugin Wrapper no longer uses the OS/2 Profile registry OS2.INI to find its location. [ . . . ]