Date: Thu, 19 May 2016 18:01:50 +0000 From: bugzilla-noreply@freebsd.org To: java@FreeBSD.org Subject: [Bug 209599] SIGSEGV in regression test suite on java/openjdk8 Message-ID: <bug-209599-8522-wIJ2NaECwC@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209599-8522@https.bugs.freebsd.org/bugzilla/> References: <bug-209599-8522@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209599 openjdk@getsnappy.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |openjdk@getsnappy.com --- Comment #10 from openjdk@getsnappy.com --- That's really interesting. It seems that if MappedByteBuffer is using Unsafe operations to load a truncated file into memory that a SEGV would be expected. I wonder how this generates an internal error on other Operating Systems. I saw a comment in the test that windows throws an error when you try to truncate a file that has an open MappedByteBuffer, maybe FreeBSD should as well. try { fc.truncate(TRUNCATED_FILE_SIZE); truncated = true; } catch (IOException ioe) { // probably on Windows where a file cannot be truncated when // there is a file mapping. truncated = false; } -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209599-8522-wIJ2NaECwC>