{"action":"created","issue":{"url":"https://api.github.com/repos/jcuda/jcuda-main/issues/3","labels_url":"https://api.github.com/repos/jcuda/jcuda-main/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/jcuda/jcuda-main/issues/3/comments","events_url":"https://api.github.com/repos/jcuda/jcuda-main/issues/3/events","html_url":"https://github.com/jcuda/jcuda-main/issues/3","id":120382533,"number":3,"title":"BasicBindingTest causes crash in cuPointerSetAttribute","user":{"login":"jcuda","id":13698062,"avatar_url":"https://avatars.githubusercontent.com/u/13698062?v=3","gravatar_id":"","url":"https://api.github.com/users/jcuda","html_url":"https://github.com/jcuda","followers_url":"https://api.github.com/users/jcuda/followers","following_url":"https://api.github.com/users/jcuda/following{/other_user}","gists_url":"https://api.github.com/users/jcuda/gists{/gist_id}","starred_url":"https://api.github.com/users/jcuda/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jcuda/subscriptions","organizations_url":"https://api.github.com/users/jcuda/orgs","repos_url":"https://api.github.com/users/jcuda/repos","events_url":"https://api.github.com/users/jcuda/events{/privacy}","received_events_url":"https://api.github.com/users/jcuda/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-12-04T11:25:51Z","updated_at":"2015-12-06T21:14:58Z","closed_at":null,"body":"This was reported as a follow-up to #2 (See the log file at https://github.com/jcuda/jcuda-main/issues/2#issuecomment-161804043 for details)\r\n\r\nThe BasicBindingTest crashes the JVM on some environments. Particularly, the crash happens in `cuPointerSetAttribute`. \r\n\r\nThe BasicBindingTest (as the name suggests) blindly calls all methods with arbitrary parameters - and maybe even invalid ones - just to see whether the methods are correctly wired in the JNI layer. This should be OK, because all errors are cought and ignored (and this should be \"handled\"). **But** if one of the underlying CUDA functions causes a crash when it receives such invalid parameters, then it may also crash the JVM, and the trace that was posted suggests that this *might* be the case here.  \r\n\r\nThere are some possible options for investigating this further. First of all, it would be interesting to see whether this only affects `cuPointerSetAttribute` or other methods as well. The conditions of the crash have to be investigated (is it caused by the parameters? or the device capabilities of the system that the method is executed on?). \r\n\r\nIn any case, it will likely be necessary to either omit the test for this particular method, or introduce a special treatment.\r\n"},"comment":{"url":"https://api.github.com/repos/jcuda/jcuda-main/issues/comments/162348111","html_url":"https://github.com/jcuda/jcuda-main/issues/3#issuecomment-162348111","issue_url":"https://api.github.com/repos/jcuda/jcuda-main/issues/3","id":162348111,"user":{"login":"jcuda","id":13698062,"avatar_url":"https://avatars.githubusercontent.com/u/13698062?v=3","gravatar_id":"","url":"https://api.github.com/users/jcuda","html_url":"https://github.com/jcuda","followers_url":"https://api.github.com/users/jcuda/followers","following_url":"https://api.github.com/users/jcuda/following{/other_user}","gists_url":"https://api.github.com/users/jcuda/gists{/gist_id}","starred_url":"https://api.github.com/users/jcuda/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jcuda/subscriptions","organizations_url":"https://api.github.com/users/jcuda/orgs","repos_url":"https://api.github.com/users/jcuda/repos","events_url":"https://api.github.com/users/jcuda/events{/privacy}","received_events_url":"https://api.github.com/users/jcuda/received_events","type":"User","site_admin":false},"created_at":"2015-12-06T21:14:58Z","updated_at":"2015-12-06T21:14:58Z","body":"OK, I found an embarassing bug here: Two of the newer functions did not call the native function at all. This is fixed now, and the basic binding test has been extended to cover this case as well. \r\n\r\nThe observed behavior is still a bit odd, since the error log *looks* like (and I would even say *indicates* that) it crashed on native side. \r\n\r\nSo at least, a severe bug has been fixed now, but I'm not *entirely* sure whether your issue is resolved as well - it would be great if you could give it a try. "}}