StdCallCallback fails with message of corrupted stack #300

Activity

1. twall

   added a commit that references this issue on Jan 12, 2014

   attempt to reproduce issue #300

   6756267
2. twall commented on Jan 12, 2014

   

   twall

   on Jan 12, 2014

   Contributor

   More actions

   Take a look at branch issue-300 to see if you can tweak it to reproduce the error you're seeing.
3. twall commented on Jan 13, 2014

   

   twall

   on Jan 13, 2014

   Contributor

   More actions

   9 arguments works, 11 arguments doesn't. Branch updated.
4. twall commented on Jan 13, 2014

   

   twall

   on Jan 13, 2014

   Contributor

   More actions

   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.
5. twall commented on Jan 13, 2014

   

   twall

   on Jan 13, 2014

   Contributor

   More actions

   Updated binaries on issue-300 branch. See if it fixes your issue.
6. boscogh commented on Jan 13, 2014

   

   boscogh

   on Jan 13, 2014

   Author

   More actions

   just tested, works perfect, thank you very much!
   would it be included in some next release?
   I would like to post solution in the forum of provider of that 3rd party dll.
   folks tried to run it through JNA unsuccesfully since 2008 year ;-)
7. twall commented on Jan 13, 2014

   

   twall

   on Jan 13, 2014

   Contributor

   More actions

   It’ll be included in the next release. It only affects w32-x86.

   On Jan 13, 2014, at 2:57 AM, boscogh notifications@github.com wrote:

   just tested, works perfect, thank you very much!
   would it be included in some next release?
   I would like to post solution in the forum of provider of that 3rd party dll.
   folks tried to run it through JNA unsuccesfully since 2008 year ;-)

   —
   Reply to this email directly or view it on GitHub.
8. twall commented on Jan 13, 2014

   

   twall

   on Jan 13, 2014

   Contributor

   More actions

   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 notifications@github.com wrote:

   just tested, works perfect, thank you very much!
   would it be included in some next release?
   I would like to post solution in the forum of provider of that 3rd party dll.
   folks tried to run it through JNA unsuccesfully since 2008 year ;-)

   —
   Reply to this email directly or view it on GitHub.
9. boscogh commented on Jan 13, 2014

   

   boscogh

   on Jan 13, 2014

   Author

   More actions

   yes, I saw the sources of your patch and I already posted on the forum of
   the 3rd party DLL (which was a part of Quik API, btw) that this was a bug
   in libffi.
   it is very cool to see such a fast patch, I am really glad to see such a
   brilliant job!

   2014/1/13 Timothy Wall notifications@github.com

   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 notifications@github.com wrote:

   just tested, works perfect, thank you very much!
   would it be included in some next release?
   I would like to post solution in the forum of provider of that 3rd party
   dll.
   folks tried to run it through JNA unsuccesfully since 2008 year ;-)

   Reply to this email directly or view it on GitHub.

   Reply to this email directly or view it on GitHubhttps://github.com//issues/300#issuecomment-32165077
   .

   Ó Õ×ÁÖÅÎÉÅÍ,
   ðÁ×ÅÌ íÁÌÀÔÉÎ
10. boscogh

    closed this as completedon Jan 13, 2014
11. mstyura

    added a commit that references this issue on Sep 9, 2024

    Make build log output less chatty (java-native-access#300)

    ...

    60c095b