9 messages in net.java.dev.jna.usersRe: [jna-users] jna segfaults on wind...
FromSent OnAttachments
Nick EvgenievJan 31, 2008 12:03 pm 
Timothy WallJan 31, 2008 1:18 pm 
Nick EvgenievFeb 1, 2008 6:29 am 
Timothy WallFeb 1, 2008 6:34 am 
Nick EvgenievFeb 1, 2008 7:07 am 
Timothy WallFeb 1, 2008 7:47 am 
Nick EvgenievFeb 4, 2008 8:14 am 
Timothy WallFeb 4, 2008 8:23 am 
Nick EvgenievFeb 4, 2008 8:37 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [jna-users] jna segfaults on windows 2003 serverActions...
From:Timothy Wall (twal@dev.java.net)
Date:Feb 1, 2008 7:47:12 am
List:net.java.dev.jna.users

It looks like SVN rev 310 used plain data memory allocation for callbacks, so that explains the issue. Current SVN rev is 478; 3.0.1 is the official release number. There's a tag and separate download in the project files section.

Definitely upgrade. There have been numerous bug fixes and a few new features since the build.xml version got bumped to 3.0. Especially if you're using stdcall convention callbacks; there was a VM crash fix for those.

On Feb 1, 2008, at 10:07 AM, Nick Evgeniev wrote:

Hi,

On Feb 1, 2008 5:35 PM, Timothy Wall <twal@dev.java.net> wrote: What version JNA are you using?

Callbacks are the only thing that use dynamically allocated executable memory, and they have been fixed on windows to avoid problems with DEP. If there's still a problem with DEP, you should file a bug report for it.

my jna is at version 3.0 (svn revision 310). Are the fixes you are talking about were made later and I should upgrade?