hyperic sigar windows 2016 & windows2019 with java sdk 1.8 compatibility issue

[battousai-dev]

i have an issue with the above setup and webpshere 8.5.5.17. The application server could not be started. The error log i got from the native_stderr.log:

Unhandled exception
Type=Segmentation error vmState=0x00040000
Windows_ExceptionCode=c0000005 J9Generic_Signal=00000004 ExceptionAddress=0000000020592BF8 ContextFlags=0010005f
Handler1=00007FFBF8EE1DA0 Handler2=00007FFBFA20CC90 InaccessibleReadAddress=0000000000000000
RDI=000000002126E940 RSI=000000002126E8C0 RAX=000000002126E380 RBX=000000002057C4E0
RCX=000000002126E380 RDX=0000000000000000 R8=0000000000000100 R9=8101010101010100
R10=80F8FCF1010100F8 R11=000000002126E380 R12=000000002126E840 R13=00007FFBF90CB740
R14=0000000000000000 R15=000000006F36E600
RIP=0000000020592BF8 RSP=000000002126DA08 RBP=000000002126E650 GS=002B
FS=0053 ES=002B DS=002B
XMM0 0000000003d92000 (f: 64561152.000000, d: 3.189745e-316)
XMM1 0000000003d9c800 (f: 64604160.000000, d: 3.191870e-316)
XMM2 0000000003d9c7f8 (f: 64604152.000000, d: 3.191869e-316)
XMM3 00007ffbf8f78b5a (f: 4176972544.000000, d: 6.952501e-310)
XMM4 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM5 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM6 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM7 0074005c003a0064 (f: 3801188.000000, d: 1.780184e-306)
XMM8 000000003f800000 (f: 1065353216.000000, d: 5.263544e-315)
XMM9 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM10 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM11 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM12 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM13 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM14 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM15 0000000000000000 (f: 0.000000, d: 0.000000e+000)
Module=D:\hyperic-sigar-1.6.4\hyperic-sigar-1.6.4\sigar-bin\lib\sigar-amd64-winnt.dll
Module_base_address=0000000020560000 Offset_in_DLL=0000000000032bf8
Target=2_90_20181219_405297 (Windows Server 2016 10.0 build 14393)
CPU=amd64 (8 logical CPUs) (0x47ff6c000 RAM)
----------- Stack Backtrace -----------
Java_org_hyperic_sigar_win32_MetaBase_MetaBaseGetMultiStringValue+0x15d8 (0x0000000020592BF8 [sigar-amd64-winnt+0x32bf8])
sigar_proc_port_get+0x111b (0x000000002056C9DB [sigar-amd64-winnt+0xc9db])
sigar_sys_info_get+0x2f (0x000000002056DB7F [sigar-amd64-winnt+0xdb7f])
Java_org_hyperic_sigar_SysInfo_gather+0xb7 (0x000000002057C597 [sigar-amd64-winnt+0x1c597])
ffi_call_win64+0x77 (win64.asm:988, 0x00007FFBF8F78BA3 [j9vm29+0xc8ba3])
ffi_call+0x9c (ffi.c:412, 0x00007FFBF8F7877C [j9vm29+0xc877c])
_ZN22VM_BytecodeInterpreter3runEP10J9VMThread+0xf40b (0x00007FFBF8F9427B [j9vm29+0xe427b])
(0x000000002126EA20)
(0x0000000025FDAF0C)
(0x0000000003D92000)
(0x0000000003D9C800)
(0x000000002126E8C0)

JVMDUMP039I Processing dump event "gpf", detail "" at 2020/04/01 04:32:04 - please wait.
JVMDUMP032I JVM requested System dump using 'D:\IBM\WebSphere\AppServer\profiles\AppSrv01\core.20200401.043204.24088.0001.dmp' in response to an event
JVMDUMP010I System dump written to D:\IBM\WebSphere\AppServer\profiles\AppSrv01\core.20200401.043204.24088.0001.dmp
JVMDUMP032I JVM requested Java dump using 'D:\IBM\WebSphere\AppServer\profiles\AppSrv01\javacore.20200401.043204.24088.0002.txt' in response to an event
JVMDUMP010I Java dump written to D:\IBM\WebSphere\AppServer\profiles\AppSrv01\javacore.20200401.043204.24088.0002.txt
JVMDUMP032I JVM requested Snap dump using 'D:\IBM\WebSphere\AppServer\profiles\AppSrv01\Snap.20200401.043204.24088.0003.trc' in response to an event
JVMDUMP010I Snap dump written to D:\IBM\WebSphere\AppServer\profiles\AppSrv01\Snap.20200401.043204.24088.0003.trc
JVMDUMP007I JVM Requesting JIT dump using 'D:\IBM\WebSphere\AppServer\profiles\AppSrv01\jitdump.20200401.043204.24088.0004.dmp'
JVMDUMP010I JIT dump written to D:\IBM\WebSphere\AppServer\profiles\AppSrv01\jitdump.20200401.043204.24088.0004.dmp
JVMDUMP013I Processed dump event "gpf", detail "".

Has anyone encounter this issue?

i tried windows 2016 with 1.7_64 java sdk, the application server successfully started with no issue.

i tried windows 2019 with 1.8_64 java sdk, same issue (application server could not be started) with windows 2016 & 1.8 java sdk.

[cnstar9988]

I fix it, because sigar use int to save pointer.
only affects 64bit latest windows.

cnstar9988/sigar@9e5dba8