Jars created with warbler trigger EMET SimExecFlow when run

[johnwunder]

As far as I can tell, every .jar or .war file that warbler creates is triggering the EMET SimExecFlow mitigation on Windows 7 (when running EMET of course). I'm not sure exactly what behavior is causing it....running the code through JRuby directly works fine, but when packaged in a JAR it suddenly turns even and EMET kills it.

Here's the simplest test case I could come up with:

1. Make sure you're running EMET
2. Create the directories and files like this:

/test
/test/bin
/test/bin/test.rb

1. Add one line to test.rb:

puts "Hi"

1. Using warbler, create the jar file:

cd /test
warble

1. Run that jar:

java -jar test.jar

Microsoft EMET shows the following error:

EMET detected SimExecFlow mitigation and will close the application: java.exe

In fact, there are two of those boxes sitting on top of each other saying the exact same thing. There's also a notice saying Java stopped unexpectedly.

OS: Windows 7 JRuby Version: 1.7.2 Warbler version: 1.4.1

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1446588-jars-created-with-warbler-trigger-emet-simexecflow-when-run?utm_campaign=plugin&utm_content=tracker%2F136961&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F136961&utm_medium=issues&utm_source=github).