Menu
▾
▴
hyperic-hq-discuss
|
From: Chakresh <sig...@hy...> - 2010-02-11 18:24:02
|
OS - Suse SLES 10 H/W - zSeries s390x Sigar - 1.6.4 JRE - IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux s390x-64 j9vmxz6423-20091104 (JIT enabled) I tried to run sigar from my java program and core dump files are created. Same program works fine with IBM jre on x86-64 hardware (OS - Fedora Linux, x86 linux sigar files). Also tried to run a test in sigar shell and it also fails. Below is the output java -jar sigar.jar test Unhandled exception Type=Floating point error vmState=0x00000000 J9Generic_Signal_Number=00080020 Signal_Number=00000008 Error_Value=00000000 Signal_Code=00000001 Handler1=0000020000306900 Handler2=00000200003702FC gpr0=0000000000000000 gpr1=0000000000000000 gpr2=0000000000000000 gpr3=000000000F4D007F gpr4=00000200218BDCB0 gpr5=000002000001DC90 gpr6=0000000080333140 gpr7=0000000000000003 gpr8=000000008032E1D0 gpr9=0000000000000001 gpr10=0000000080332E90 gpr11=000003FFFF940C80 gpr12=000002000001E000 gpr13=0000020000017348 gpr14=0000020000009D84 gpr15=000003FFFF940B98 psw=0000020000009908 mask=0705C00180000000 fpc=0008000000000000 fpr0 4240000000000000 (f: 0.000000, d: 1.374390e+11) fpr1 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr2 3f40000000000000 (f: 0.000000, d: 4.882812e-04) fpr3 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr4 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr5 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr6 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr7 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr8 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr9 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr10 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr11 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr12 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr13 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr14 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr15 0000000000000000 (f: 0.000000, d: 0.000000e+00) Module=/lib64/ld64.so.1 Module_base_address=0000020000000000 Target=2_30_20091103_45935_BHdSMr (Linux 2.6.16.60-0.54.5-default) CPU=s390x (1 logical CPUs) (0x3e43c000 RAM) JVMDUMP006I Processing dump event "gpf", detail "" - please wait. JVMDUMP032I JVM requested System dump using '/opt/nsAgent/lib/core.20100210.223924.8705.0001.dmp' in response to an event JVMDUMP010I System dump written to /opt/nsAgent/lib/core.20100210.223924.8705.0001.dmp JVMDUMP032I JVM requested Snap dump using '/opt/nsAgent/lib/Snap.20100210.223924.8705.0002.trc' in response to an event JVMDUMP010I Snap dump written to /opt/nsAgent/lib/Snap.20100210.223924.8705.0002.trc JVMDUMP032I JVM requested Java dump using '/opt/nsAgent/lib/javacore.20100210.223924.8705.0003.txt' in response to an event JVMDUMP010I Java dump written to /opt/nsAgent/lib/javacore.20100210.223924.8705.0003.txt JVMDUMP013I Processed dump event "gpf", detail "". I will be happy to provide core/snap files, if needed. Could anyone please help to find out what is the issue here ? Thanks |
|
From: Doug M. <do...@hy...> - 2010-02-16 18:07:13
|
Hi, We haven't seen any issues using the 1.6 jre on s390x: IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux s390x-64 jvmxz6460-20080416_18762 (JIT enabled, AOT enabled) Can you try with a 1.6 jre? |
|
From: Chakresh <sig...@hy...> - 2010-02-17 05:02:38
|
Hi Doug, Thanks for reply. I tried running 1.6.3 sigar with IBM 1.6 jre but still it fails. Below is the output etpgluz:/opt/newfiles/hyperic-sigar-1.6.3/sigar-bin/lib # /opt/ibm/java-s390x-60/jre/bin/java -version java version "1.6.0" Java(TM) SE Runtime Environment (build pxz6460sr7-20091215_02(SR7)) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux s390x-64 jvmxz6460sr7-20091214_49398 (JIT enabled, AOT enabled) J9VM - 20091214_049398 JIT - r9_20091123_13891 GC - 20091111_AA) JCL - 20091202_01 etpgluz:/opt/newfiles/hyperic-sigar-1.6.3/sigar-bin/lib # /opt/ibm/java-s390x-60/jre/bin/java -jar sigar.jar test Unhandled exception Type=Floating point error vmState=0x00000000 J9Generic_Signal_Number=00080020 Signal_Number=00000008 Error_Value=00000000 Signal_Code=00000001 Handler1=0000020000ABC7D4 Handler2=0000020000B4DFA4 gpr0=0000000000000000 gpr1=0000000000000000 gpr2=0000000000000000 gpr3=000000000F4D007F gpr4=00000200223F0CB0 gpr5=000002000001DC90 gpr6=0000000080557290 gpr7=0000000000000003 gpr8=0000000080558830 gpr9=0000000000000001 gpr10=0000000080556FE0 gpr11=0000020000A76FA0 gpr12=000002000001E000 gpr13=0000020000017348 gpr14=0000020000009D84 gpr15=0000020000A76EB8 psw=0000020000009908 mask=0705C00180000000 fpc=0008000000000000 fpr0 42c0000000000000 (f: 0.000000, d: 3.518437e+13) fpr1 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr2 4040000000000000 (f: 0.000000, d: 3.200000e+01) fpr3 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr4 3ff3333333333333 (f: 858993472.000000, d: 1.200000e+00) fpr5 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr6 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr7 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr8 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr9 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr10 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr11 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr12 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr13 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr14 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr15 0000000000000000 (f: 0.000000, d: 0.000000e+00) Module=/lib64/ld64.so.1 Module_base_address=0000020000000000 Target=2_40_20091214_049398 (Linux 2.6.16.60-0.54.5-default) CPU=s390x (1 logical CPUs) (0x3e43c000 RAM) ----------- Stack Backtrace ----------- (0x0000020000B4437A [libj9prt24.so+0x0]) --------------------------------------- JVMDUMP006I Processing dump event "gpf", detail "" - please wait. JVMDUMP032I JVM requested System dump using '/opt/newfiles/hyperic-sigar-1.6.3/sigar-bin/lib/core.20100216.140249.27930.0001.dmp' in response to an event JVMDUMP010I System dump written to /opt/newfiles/hyperic-sigar-1.6.3/sigar-bin/lib/core.20100216.140249.27930.0001.dmp JVMDUMP032I JVM requested Snap dump using '/opt/newfiles/hyperic-sigar-1.6.3/sigar-bin/lib/Snap.20100216.140249.27930.0002.trc' in response to an event JVMDUMP010I Snap dump written to /opt/newfiles/hyperic-sigar-1.6.3/sigar-bin/lib/Snap.20100216.140249.27930.0002.trc JVMDUMP032I JVM requested Java dump using '/opt/newfiles/hyperic-sigar-1.6.3/sigar-bin/lib/javacore.20100216.140249.27930.0003.txt' in response to an event JVMDUMP010I Java dump written to /opt/newfiles/hyperic-sigar-1.6.3/sigar-bin/lib/javacore.20100216.140249.27930.0003.txt JVMDUMP013I Processed dump event "gpf", detail "". Please let me know if you need more information. I have urgency to get sigar working with IBM java. Appreciate all your help. Thanks Chakresh |
|
From: Doug M. <do...@hy...> - 2010-02-16 23:28:51
|
If you could: gzip javacore.20100216.140249.27930.0003.txt And attach javacore.20100216.140249.27930.0003.txt.gz I'll take a look. |
|
From: Chakresh <sig...@hy...> - 2010-02-17 05:02:38
|
Doug, Attaching the requested file. Thanks |
|
From: Doug M. <do...@hy...> - 2010-02-17 02:35:09
|
Looks like the JVM is crashing trying to load libsigar-s390x-linux.so. What is the output of the following commands: % md5sum libsigar-s390x-linux.so % ldd libsigar-s390x-linux.so % strings libsigar-s390x-linux.so | grep SIGAR- |
|
From: Chakresh <sig...@hy...> - 2010-02-17 05:02:43
|
etpgluz:# md5sum libsigar-s390x-linux.so
c1b835fbeed0ab9cfd5d0716dbf3942b libsigar-s390x-linux.so
etpgluz:# ldd libsigar-s390x-linux.so
libc.so.6 => /lib64/libc.so.6 (0x000002000005a000)
/lib/ld64.so.1 (0x000002aaaaaaa000)
etpgluz:# strings libsigar-s390x-linux.so | grep SIGAR-
SIGAR-1.6.3.1, SCM revision 80016c6, built 07/09/2009 07:16 AM as libsigar-s390x-linux.so
Thanks
|
|
From: Doug M. <do...@hy...> - 2010-02-17 19:32:25
|
That looks fine. One more command that might shed some light on the problem: % strace -f -o strace.txt java -jar sigar.jar version And attach strace.txt Another option would be to try building Sigar from source: http://support.hyperic.com/display/SIGAR/Home#Home-building Can you give that try? |
|
From: Chakresh <sig...@hy...> - 2010-02-21 18:32:51
|
Doug I ran this command "strace -f -o strace.txt /opt/ibm/java-s390x-60/jre/bin/java -jar sigar.jar version" and attaching stack trace file for the same. Thanks |
|
From: Chakresh <sig...@hy...> - 2010-02-21 18:32:54
|
Doug I compiled the source and was able to generate sigar.jar and libsigar-s390x-linux.so. Tried running 2 commands and below is the output (looks like there is some progress) etpgluz:/opt/sigar/hyperic-sigar-1.6.3-src/bindings/java/sigar-bin/lib # /opt/ibm/java-s390x-60/jre/bin/java -jar sigar.jar version Sigar version.......java=1.6.3.0, native=1.6.3.0 Build date..........java=02/17/2010 05:08 PM, native=02/17/2010 05:08 PM SCM rev.............java=exported, native=exported Archlib.............libsigar-s390x-linux.so Current fqdn........etpgluz.dal-ebis.ihost.com Hostname............etpgluz Current user........root OS description......SuSE 10 OS name.............Linux OS arch.............s390x OS machine..........s390x OS version..........2.6.16.60-0.54.5-default OS patch level......unknown OS vendor...........SuSE OS vendor version...10 OS code name........ OS data model.......64 OS cpu endian.......null Java vm version.....2.4 Java vm vendor......IBM Corporation Java home.........../opt/ibm/java-s390x-60/jre etpgluz:/opt/sigar/hyperic-sigar-1.6.3-src/bindings/java/sigar-bin/lib # /opt/ibm/java-s390x-60/jre/bin/java -jar sigar.jar test unknown command: test Is this the expected output for test command? I am wondering what change happened by compiling on this machine? Please let me know if you want me to try some other things. Thanks |
|
From: Chakresh <sig...@hy...> - 2010-02-23 04:28:16
|
Hi Doug I tried to use the new sigar files (compiled on zVM A) on another machine (zVM B) and again i am running into core dump issue. Can you help me out here as to why this is happening? Both machines are 64 bit (s390x). Appreciate all your help Thanks Chakresh |
|
From: Chakresh <sig...@hy...> - 2010-02-23 04:28:16
|
This time the error reports different information Unhandled exception Type=Segmentation error vmState=0x00000000 J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=3bb4f538 Signal_Code=0000 0001 Handler1=00000200002A4900 Handler2=00000200003122FC InaccessibleAddress=00000000238C9000 gpr0=0000000000000020 gpr1=00000000238C9E90 gpr2=0000000080030800 gpr3=0000020023A2DA2E gpr4=0000020023A0CB04 gpr5=0000000000000020 gpr6=3D4CCCD000000000 gpr7=00000200225EC128 gpr8=0000000000000007 gpr9=00000200225EC158 gpr10=00000200225EC158 gpr11=0000000080030800 gpr12=0000000000000000 gpr13=0000000080030800 gpr14=0000020023A0CB04 gpr15=000003FFFFFFD338 psw=0000020023A0CB1A mask=0705E00180000000 fpc=0008000000000000 fpr0 428e800000000000 (f: 0.000000, d: 4.191888e+12) fpr1 3f40000000000000 (f: 0.000000, d: 4.882812e-04) fpr2 3f40000000000000 (f: 0.000000, d: 4.882812e-04) fpr3 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr4 3f73333300000000 (f: 0.000000, d: 4.687499e-03) fpr5 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr6 3d4cccd000000000 (f: 0.000000, d: 2.046367e-13) fpr7 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr8 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr9 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr10 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr11 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr12 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr13 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr14 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr15 0000000000000000 (f: 0.000000, d: 0.000000e+00) Module=/opt/nsol/nsAaka/agents/nsAgent/lib/libsigar-s390x-linux.so Module_base_address=0000020023A00000 Target=2_30_20091103_45935_BHdSMr (Linux 2.6.5-7.308-s390x) CPU=s390x (2 logical CPUs) (0x139adc000 RAM) JVMDUMP006I Processing dump event "gpf", detail "" - please wait. JVMDUMP032I JVM requested System dump using '/opt/nsol/nsAaka/bin/core.20100222.180522.17981. 0001.dmp' in response to an event JVMDUMP010I System dump written to /opt/nsol/nsAaka/bin/core.20100222.180522.17981.0001.dmp JVMDUMP032I JVM requested Snap dump using '/opt/nsol/nsAaka/bin/Snap.20100222.180522.17981.00 02.trc' in response to an event JVMDUMP010I Snap dump written to /opt/nsol/nsAaka/bin/Snap.20100222.180522.17981.0002.trc JVMDUMP032I JVM requested Java dump using '/opt/nsol/nsAaka/bin/javacore.20100222.180522.1798 1.0003.txt' in response to an event JVMDUMP010I Java dump written to /opt/nsol/nsAaka/bin/javacore.20100222.180522.17981.0003.txt JVMDUMP013I Processed dump event "gpf", detail "". |
|
From: Chakresh <sig...@hy...> - 2010-02-23 18:14:26
|
Hi Doug Update - running test command on sigar.jar with s390x.so gave the output but it crashed immediately after that (the target server is a 64-bit machine). A snanpshot of javacore file "3XMTHREADINFO "main" (TID:0x0000000080032800, sys_thread_t:0x000000008001B030, state:R, native ID:0x0000000000004A99) prio=5 4XESTACKTRACE at org/hyperic/sigar/Sigar.nativeClose(Native Method) 4XESTACKTRACE at org/hyperic/sigar/Sigar.close(Sigar.java:229) 4XESTACKTRACE at org/hyperic/sigar/cmd/Shell.shutdown(Shell.java:196) 4XESTACKTRACE at org/hyperic/sigar/cmd/Shell.main(Shell.java:230) 4XESTACKTRACE at sun/reflect/NativeMethodAccessorImpl.invoke0(Native Method) 4XESTACKTRACE at sun/reflect/NativeMethodAccessorImpl.invoke(NativeMethodAccessorImp l.java:79)" Also (as in previous post) there is a segmentation error and inaccessible memory address. I tried running 31-bit sigar files on this server and they run fine. Looks like it could be a machine configuration issue. Talked to IBM support and they recommend using the -fPIC flag for compilation and linking and test it out. I am not well versed with build configuration , so can you help me out where i can specify the flags for building sigar files. Thanks Chakresh |
|
From: Doug M. <do...@hy...> - 2010-02-24 19:16:57
|
Hi Chakresh,
There is a classpath issue running the 'test' command, you can workaround with:
cp lib/*.jar sigar-bin/lib
Clearly our binary compiled on RHEL 5.2 is not compatible with your SLES 10 system, unclear why however.
Is zVM A and B running the same OS?
The sources are compiled with -fPIC btw, see:
ant -verbose 2>&1 | grep fPIC
[cc] gcc -O2 -Wall -m64 -c -fPIC ...
-Doug
|
|
From: Chakresh <sig...@hy...> - 2010-02-26 17:45:15
|
Hi Doug Thanks for the response. zVM A and zVM B are running SLES9 and are 64-bit kernel servers. I compiled both 390 and s390x sigar files on SLES9 in our lab and they work fine on zVM A but on zVM B only s390 version works. When i try to run s390x sigar files, i do get the output for the version command but after that i get JVM crash. Below is the output suse04:/opt/nsol/build/hyperic-sigar-1.6.3-src/bindings/java/sigar-bin/lib # /opt/ibm/java2-s390x-50/jre/bin/java -jar sigar.jar version Sigar version.......java=1.6.3.0, native=1.6.3.0 Build date..........java=02/22/2010 09:33 PM, native=02/22/2010 09:33 PM SCM rev.............java=exported, native=exported Archlib.............libsigar-s390x-linux.so Current fqdn........suse04.dpf.gov.br Hostname............suse04 Current user........root OS description......SuSE 9 OS name.............Linux OS arch.............s390x OS machine..........s390x OS version..........2.6.5-7.308-s390x OS patch level......unknown OS vendor...........SuSE OS vendor version...9 OS code name........ OS data model.......64 OS cpu endian.......null Java vm version.....2.3 Java vm vendor......IBM Corporation Java home.........../opt/ibm/java2-s390x-50/jre Unhandled exception Type=Segmentation error vmState=0x00000000 J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=3b339738 Signal_Code=00000001 Handler1=00000200002A2B04 Handler2=00000200002F9EE4 InaccessibleAddress=0000000022936000 gpr0=0000000000000020 gpr1=00000000229364F0 gpr2=000000008002CB00 gpr3=0000020022A2D9FE gpr4=0000020022A0CB04 gpr5=0000000000000020 gpr6=0000000000000001 gpr7=00000200225F5E10 gpr8=000000008002CB00 gpr9=00000200225F5E10 gpr10=00000200225F5E10 gpr11=000000008002CB00 gpr12=0000000000000000 gpr13=000000008002CB00 gpr14=0000020022A0CB04 gpr15=000003FFFFFFDF40 psw=0000020022A0CB1A mask=0705E00180000000 fpc=0008000000000000 fpr0 428e800000000000 (f: 0.000000, d: 4.191888e+12) fpr1 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr2 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr3 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr4 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr5 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr6 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr7 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr8 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr9 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr10 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr11 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr12 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr13 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr14 0000000000000000 (f: 0.000000, d: 0.000000e+00) fpr15 0000000000000000 (f: 0.000000, d: 0.000000e+00) Module=/opt/nsol/build/hyperic-sigar-1.6.3-src/bindings/java/sigar-bin/lib/libsigar-s390x-linux.so Module_base_address=0000020022A00000 Target=2_30_20060915_08260_BHdSMr (Linux 2.6.5-7.308-s390x) CPU=s390x (2 logical CPUs) (0x139adc000 RAM) JVMDUMP006I Processing Dump Event "gpf", detail "" - Please Wait. Looking at the javacore file, below is a snippet NULL ------------------------------------------------------------------------ 0SECTION THREADS subcomponent dump routine NULL ================================= NULL 1XMCURTHDINFO Current Thread Details NULL ---------------------- 3XMTHREADINFO "main" (TID:0x0000000080032800, sys_thread_t:0x000000008001B030, state:R, native ID:0x0000000000004A99) prio=5 4XESTACKTRACE at org/hyperic/sigar/Sigar.nativeClose(Native Method) 4XESTACKTRACE at org/hyperic/sigar/Sigar.close(Sigar.java:229) 4XESTACKTRACE at org/hyperic/sigar/cmd/Shell.shutdown(Shell.java:196) 4XESTACKTRACE at org/hyperic/sigar/cmd/Shell.main(Shell.java:230) 4XESTACKTRACE at sun/reflect/NativeMethodAccessorImpl.invoke0(Native Method) 4XESTACKTRACE at sun/reflect/NativeMethodAccessorImpl.invoke(NativeMethodAccessorImp l.java:79) 4XESTACKTRACE at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcc essorImpl.java:43) 4XESTACKTRACE at java/lang/reflect/Method.invoke(Method.java:618) 4XESTACKTRACE at org/hyperic/sigar/cmd/Runner.main(Runner.java:214(Compiled Code)) Please let me know if you need any other information. Appreciate your help Thanks Chakresh |
|
From: Doug M. <do...@hy...> - 2010-02-24 19:53:46
|
The original crash happens in the JVM, when using the distribution binary on your system. This crash is clearly happening within the sigar code. If you could do the following, we can see exactly where it's happening: % ant -Djni.debug=true % gdb `which java` (gdb) run -jar sigar-bin/lib/sigar.jar test Assuming this crashes, the last few lines of output should include the filename:linenumber of the crash. |
|
From: Chakresh <sig...@hy...> - 2010-02-26 17:45:21
|
Hi Doug
Sorry for confusing you with other outputs. I copied the jar files as you suggested and ran test command under gdb, It point to line 208 in javasigar.c
OS vendor...........SuSE
OS vendor version...10
OS code name........
OS data model.......64
OS cpu endian.......null
Java vm version.....2.3
Java vm vendor......IBM Corporation
Java home.........../opt/nsol/nsAaka/common/tptools/ibm/LINUX/jre1.5
TestLog.testCreate.........................ok
TestInvoker.testCreate.....................
Program received signal SIGSEGV, Segmentation fault.
---Type <return> to continue, or q <return> to quit---
[Switching to Thread 2199025135696 (LWP 4218)]
0x00000200219e2d7e in sigar_get_jpointer (env=0x8002f200, obj=0x801d13a0)
at /opt/nsol/build/hyperic-sigar-1.6.3-src/bindings/java/src/jni/javasigar.c:208
208 if (jsigar->open_status != SIGAR_OK) {
Backtrace output
(gdb) backtrace
#0 0x00000200219e2d7e in sigar_get_jpointer (env=0x8002f200, obj=0x801d13a0)
at /opt/nsol/build/hyperic-sigar-1.6.3-src/bindings/java/src/jni/javasigar.c:208
#1 0x00000200219eab5c in Java_org_hyperic_sigar_Mem_gather (env=0x8002f200,
obj=0x801d13a8, sigar_obj=0x801d13a0)
at /opt/nsol/build/hyperic-sigar-1.6.3-src/bindings/java/build/src/javasigar_generated.c:561
#2 0x00000200002cdccc in L48 ()
from /opt/nsol/nsAaka/common/tptools/ibm/LINUX/jre1.5/bin/libj9vm23.so
#3 0x000002000027df00 in JVM_InvokeMethod ()
from /opt/nsol/nsAaka/common/tptools/ibm/LINUX/jre1.5/bin/j9vm/libjvm.so
#4 0x0000020000025360 in JVM_InvokeMethod ()
from /opt/nsol/nsAaka/common/tptools/ibm/LINUX/jre1.5/bin/classic/libjvm.so
#5 0x000002002168ef86 in Java_sun_reflect_NativeMethodAccessorImpl_invoke0 ()
from /opt/nsol/nsAaka/common/tptools/ibm/LINUX/jre1.5/bin/libjava.so
#6 0x000002002057ef74 in ?? ()
#7 0x000002000027df00 in JVM_InvokeMethod ()
from /opt/nsol/nsAaka/common/tptools/ibm/LINUX/jre1.5/bin/j9vm/libjvm.so
Another issue is that i have access to this specific machine only for 1 more day, so if you want me to run more tests, please let me know
Thanks
Chakresh
|
|
From: Chakresh <sig...@hy...> - 2010-02-26 18:17:06
|
Hi Doug Running with gdb did not crash. Below is snapshot of the screen [New Thread 2199584782672 (LWP 17758)] [New Thread 2199584815440 (LWP 17759)] [New Thread 2199584848208 (LWP 17760)] Sigar version.......java=1.6.3.0, native=1.6.3.0 Build date..........java=02/22/2010 09:33 PM, native=02/24/2010 05:11 PM SCM rev.............java=exported, native=exported Archlib.............libsigar-s390x-linux.so Current fqdn........suse27.dpf.gov.br Hostname............suse27 Current user........root OS description......SuSE 10 OS name.............Linux OS arch.............s390x OS machine..........s390x OS version..........2.6.16.27-0.9-default OS patch level......unknown OS vendor...........SuSE OS vendor version...10 OS code name........ OS data model.......64 OS cpu endian.......null Java vm version.....2.3 Java vm vendor......IBM Corporation Java home.........../opt/nsol/nsAaka/common/tptools/ibm/LINUX/jre1.5 [New Thread 2199587649872 (LWP 17761)] [Thread 2199584782672 (zombie) exited] [Thread 2199587649872 (zombie) exited] [Thread 2199584815440 (zombie) exited] [Thread 2199584848208 (zombie) exited] [Thread 2199583697232 (zombie) exited] [Thread 2199583730000 (zombie) exited] Program exited normally. (gdb) q suse27:/opt/nsol/build/hyperic-sigar-1.6.3-src/bindings/java/sigar-bin/lib # ll total 993 -rw-r--r-- 1 rafael.rzm users 586131 Feb 24 17:11 libsigar-s390x-linux.so -rw-r--r-- 1 rafael.rzm users 423878 Feb 24 17:11 sigar.jar |
|
From: Chakresh <sig...@hy...> - 2010-02-26 17:45:17
|
Hi Doug
Looking at the output for ant verbose, i see that compilation is done with fPIC flag but not linking. Do you suspect this could be an issue?
[cc] gcc -O2 -Wall -m64 -c -fPIC -DSIGAR_LINUX -D_REENTRANT -I/opt/nsolutions/sigar-test-compile/hyperic-sigar-1.6.3-src/include -I/opt/nsolutions/sigar-
test-compile/hyperic-sigar-1.6.3-src/src/os/linux -I/opt/nsolutions/sigar-test-compile/hyperic-sigar-1.6.3-src/bindings/java/build/src -I/opt/nsolutions/sigar-t
est-compile/hyperic-sigar-1.6.3-src/bindings/java/src/jni -I/opt/ibm/java2-s390x-50/include -I/opt/ibm/java2-s390x-50/include/linux /opt/nsolutions/sigar-test-c
ompile/hyperic-sigar-1.6.3-src/bindings/java/build/src/sigar_version.c
[cc] Starting link
[cc] gcc -m64 -shared -o libsigar-s390x-linux.so ../vmcontrol_wrapper.o ../javasigar.o ../sigar_signal.o ../sigar_util.o ../sigar_version.o ../sigar.o ..
/sigar_format.o ../linux_sigar.o ../sigar_cache.o ../sigar_fileinfo.o ../sigar_ptql.o ../javavmware.o ../sigar_getline.o
Can you help me how i can do linking also with fPIC flag?
thanks
Chakresh
|
|
From: Doug M. <do...@hy...> - 2010-03-04 22:28:34
|
Hi Chakresh,
Apologies for the delayed response. Not sure if adding -fPIC to the linker flags will help, but you can just add '<linkerarg value="-fPIC"/>' to the linux linker section in jni-build.xml:
--- a/bindings/java/hyperic_jni/jni-build.xml
+++ b/bindings/java/hyperic_jni/jni-build.xml
@@ -345,16 +345,17 @@ USA.
<linker name="gcc" if="linux">
<libset if="jni.libset.libs"
dir="${jni.libset.dir}"
libs="${jni.libset.libs}"/>
<libset if="jni.dmalloc"
dir="${jni.dmalloc}/lib"
libs="dmallocth"/>
<linkerarg value="${jni.gccm}" if="jni.gccm"/>
+ <linkerarg value="-fPIC"/>
</linker>
|
|
From: Chakresh <sig...@hy...> - 2010-03-05 01:16:47
|
Hi Doug I did try that before and it did not help. Did you got a chance to look at the gdb output i sent you earlier? thanks Chakresh |
|
From: uywfhoi <uwh...@ya...> - 2010-11-17 07:15:46
|
GMs shouldn't be surprised to see healers who are not happy with the new healing model stop playing by the [url=http://www.storeingame.com/]WOW Gold[/url]. By the reverse token, there might be some new players who will love the new healing model and will thrive on it. The ultimate end goal is to make healing as fun as possible for as many different players where could [url=http://www.zyy.com/]Buy WOW Gold[/url]. If there is a wider appeal, then there are bound to be more healers! Are we going to see the implementation of a healing rotation during raids? Is this going to be "fun" for healers? We have very available stock of WOW [url=http://www.gobuycheaprsgold.com]RS Gold[/url] on most of the servers and we can deliver your WOW gold on the order in a short while. The idea of a healing "rotation" isn't unheard of.That trend came from DPS players, who would use a precise sequence of spells in order to maximize [url=http://www.storeingame.com/level/World-of-Warcraft-EU/power-leveling/]WOW Power Leveling[/url] DPS. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X