-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
StdCallCallback fails with message of corrupted stack #300
Comments
Take a look at branch |
9 arguments works, 11 arguments doesn't. Branch updated. |
libffi may be calculating an incorrect stack size (actual 60, expected 56). This number is inserted into a dynamically generated trampoline, defined in libffi/src/x86/ffi.c. My expectation may be off. |
Updated binaries on issue-300 branch. See if it fixes your issue. |
just tested, works perfect, thank you very much! |
It’ll be included in the next release. It only affects w32-x86. On Jan 13, 2014, at 2:57 AM, boscogh [email protected] wrote:
|
BTW, this is a bug in the underlying libffi library, so a patch will be forwarded to that project as well. On Jan 13, 2014, at 2:57 AM, boscogh [email protected] wrote:
|
yes, I saw the sources of your patch and I already posted on the forum of 2014/1/13 Timothy Wall [email protected]
Ó Õ×ÁÖÅÎÉÅÍ, |
Motivation: When Maven does not run in batch mode, it will continuously print its progress as it downloads dependencies. This can produce a very large amount of log output, that makes it harder to debug build failures. Modification: - Make all Maven builds run in batch mode by adding the -B command line flag. - Some builds were already running batch mode but had the flag in a different location – these have had their -B flag moved so all builds are consistent. - Add -ntp flag Result: Much less output in our build logs where Maven is just downloading stuff.
I found out use case there StdCallCallback fails with message of corrupted stack.
It only occure with method of specific signature.
Please review my question on stackoverflow, it contains isolated testcase to 100% reproducible issue
link to the question details with source code included:
http://stackoverflow.com/questions/21039368/jna-stdcall-esp-corruption
The text was updated successfully, but these errors were encountered: