Community
Participate
Working Groups
Port is done and half of getting build is in place. Need a bugzilla to check in against, adn I couldn't find one.
Need sources passed so that they can be built.
Checked in 4 makefile.win_{ipf|em64t} and 9 *.mak64 files.
Build now in place, and building for Windows-IPF and Windows-EM64T... but can't close as Linux builds aren't done yet.
Randy, What was the porting change that you had to make here? Thanks
Pushing out to i4 as this is just a build issue in support of Tech Preview JVMTI.
Guru, As detailed in Comment #2, the only real change was in build support. I added makefile.win_{ipf|em64t} driver scripts and .mak64 makefiles to build and package what I needed (a probekit.<os>_<platform>.zip file that contained the two dynamic link libraries) as an interim step in building the agntctrl packages. No code was ported... only build support.
EM64T and IPF ports done and building for Windows, but still need for Linux. Since new tech AC not the default AC for Linux here, pushing out to 4.3, and changing title to indicate more restricted target now.
Retargeting to future. This is needed for completing the backwards compatibility on Linux IPF and EM64T which is not in 4.3 plan do to lack of resource.
*** Bug 158098 has been marked as a duplicate of this bug. ***
Minor patch attached here as https://bugs.eclipse.org/bugs/attachment.cgi?id=50622 "org.eclipse.hyades.probekit.diff" as an update to Bug #157482 Are there Unit tests for the native part of BCI/ProbeKit that I can perform on 64bit Linux ?
No, there are no unit tests. We have Automated GUI Recorder (AGR) test suites to automatically test both the native as well as the Java code.
Transferring general agent controller enhancement requests to new project lead (Joanna) for consideration in future releases.
Please work with Liz and OC systems to determine the effort required given that BCI is already ported to the platforms in context, the JVMTI agent is being extended to support Probekit and this is available on all the 6 platforms (Win & Linux (32, 64 bit(Itanium & x64))), and the remaining work involves porting the Probekit native code to these platforms.
Since BCI has already been ported to Linux IPF and EM64T, I'm reassigning this to Vsevolod so he takes it into account when developing the JVMTI agent extension for Probekit.
This defect is currently blocked by defect 182347 which causes the agent controller to crash on EM64T during profiling, thus blocking testing of our JVMTI Probekit build on EM64T.
I have tested the Windows EM64T build on the 200705310943 driver and found that the decoder is registering 0 bytes. Here is the output: [PROBEKIT MPICL_Instantiate] [PROBEKIT InitEC] [PROBEKIT EC Attach] [PROBEKIT EC Start] [PROBEKIT EC Start] [PROBEKIT Initialize BCI Instrumenter, options=ext-pk-BCILibraryName=BCIEngProbe] [PROBEKIT BCIEngine=BCIEngProbe] [PROBEKIT PROBEKIT_DATA_0=3srswAAAABNteXByb2JlLnByb2Jlc2NyaXB0AAAC+1JFTSB1bm5hbWVkX3Byb2JlAABQUk9CRQAA UkVGIE9ORU5UUlkgbXlwcm9iZV9wcm9iZSRQcm9iZV8wIF9lbnRyeSAoTGphdmEvbGFuZy9TdHJpbmc7KVYgY2xhc3NOYW1lAFJVTEUgIGNvbSBpYm0qICogKiBFWENMVURFAFJVTEUgIGNvbS5pYm0qICogKiAqIEVYQ0xVREUAUlVMRSAgY29tIHN1biogKiAqIEVYQ0xVREUAUlVMRSAgY29tLnN1biogKiAqICogRVhDTFVERQBSVUxFICBDT00gaWJtKiAqICogRVhDTFVERQBSVUxFICBDT00uaWJtKiAqICogKiBFWENMVURFAFJVTEUgIGphdmEqICogKiAqIEVYQ0xVREUAUlVMRSAgLiBqYXZhKiAqICogRVhDTFVERQBSVUxFICBvcmcqICogKiAqIEVYQ0xVREUAUlVMRSAgLiBvcmcqICogKiBFWENMVURFAFJVTEUgIHN1biogKiAqICogRVhDTFVERQBSVUxFICAuIHN1biogKiAqIEVYQ0xVREUARklMVEVSICBjb20gaWJtKiAqICogRVhDTFVERQBGSUxURVIgIGNvbS5pYm0qICogKiAqIEVYQ0xVREUARklMVEVSICBjb20gc3VuKiAqICogRVhDTFVERQBGSUxURVIgIGNvbS5zdW4qICogKiAqIEVYQ0xVREUARklMVEVSICBDT00gaWJtKiAqICogRVhDTFVERQBGSUxURVIgIENPTS5pYm0qICogKiAqIEVYQ0xVREUARklMVEVSICBqYXZhKiAqICogKiBFWENMVURFAEZJTFRFUiAgLiBqYXZhKiAqICogRVhDTFVERQBGSUxURVIgIG9yZyogKiAqICogRVhDTFVERQBGSUxURVIgIC4gb3JnKiAqICogRVhDTFVERQBGSUxURVIgIHN1biogKiAqICogRVhDTFVERQBGSUxURVIgIC4gc3VuKiAqICogRVhDTFVERQAAAAAbbXlwcm9iZV9wcm9iZSRQcm9iZV8wLmNsYXNzAAAC9sr+ur4AAAAxADEHAAIBABVteXByb2JlX3Byb2JlJFByb2JlXzAHAAQBABBqYXZhL2xhbmcvT2JqZWN0AQAGPGluaXQ+AQADKClWAQAEQ29kZQoAAwAJDAAFAAYBAA9MaW5lTnVtYmVyVGFibGUBABJMb2NhbFZhcmlhYmxlVGFibGUBAAR0aGlzAQAXTG15cHJvYmVfcHJvYmUkUHJvYmVfMDsBAAZfZW50cnkBABUoTGphdmEvbGFuZy9TdHJpbmc7KVYJABEAEwcAEgEAEGphdmEvbGFuZy9TeXN0ZW0MABQAFQEAA291dAEAFUxqYXZhL2lvL1ByaW50U3RyZWFtOwcAFwEAF2phdmEvbGFuZy9TdHJpbmdCdWlsZGVyCAAZAQAEaGVyZQoAFgAbDAAFAA8KABYAHQwAHgAfAQAGYXBwZW5kAQAtKExqYXZhL2xhbmcvU3RyaW5nOylMamF2YS9sYW5nL1N0cmluZ0J1aWxkZXI7CgAWACEMACIAIwEACHRvU3RyaW5nAQAUKClMamF2YS9sYW5nL1N0cmluZzsKACUAJwcAJgEAE2phdmEvaW8vUHJpbnRTdHJlYW0MACgADwEAB3ByaW50bG4BAAthY2xhc3NOYW1lMAEAEkxqYXZhL2xhbmcvU3RyaW5nOwEAClNvdXJjZUZpbGUBABJteXByb2JlX3Byb2JlLmphdmEBAAxJbm5lckNsYXNzZXMHAC8BAA1teXByb2JlX3Byb2JlAQAHUHJvYmVfMAAhAAEAAwAAAAAAAgABAAUABgABAAcAAAAvAAEAAQAAAAUqtwAIsQAAAAIACgAAAAYAAQAAAAcACwAAAAwAAQAAAAUADAANAAAACQAOAA8AAQAHAAAARQAEAAEAAAAXsgAQuwAWWRIYtwAaKrYAHLYAILYAJLEAAAACAAoAAAAKAAIAAAAMABYADgALAAAADAABAAAAFwApACoAAAACACsAAAACACwALQAAAAoAAQABAC4AMAAJAAAAE215cHJvYmVfcHJvYmUuY2xhc3MAAAFMyv66vgAAADEAFAcAAgEADW15cHJvYmVfcHJvYmUHAAQBABBqYXZhL2xhbmcvT2JqZWN0AQAGPGluaXQ+AQADKClWAQAEQ29kZQoAAwAJDAAFAAYBAA9MaW5lTnVtYmVyVGFibGUBABJMb2NhbFZhcmlhYmxlVGFibGUBAAR0aGlzAQAPTG15cHJvYmVfcHJvYmU7AQAKU291cmNlRmlsZQEAEm15cHJvYmVfcHJvYmUuamF2YQEADElubmVyQ2xhc3NlcwcAEgEAFW15cHJvYmVfcHJvYmUkUHJvYmVfMAEAB1Byb2JlXzAAIAABAAMAAAAAAAEAAAAFAAYAAQAHAAAALwABAAEAAAAFKrcACLEAAAACAAoAAAAGAAEAAAAFAAsAAAAMAAEAAAAFAAwADQAAAAIADgAAAAIADwAQAAAACgABABEAAQATAAk=] [PROBEKIT total len = 2598] [PROBEKIT decoded 0 bytes, magic=-557126464] [PROBEKIT MPICL_Instantiate done] [PROBEKIT VM Init] [PROBEKIT CBCIInstrumenter::OnVMInit]
(In reply to comment #16) You're using an old build of ProbekitAgent.dll. If this is an official build, how do you get the debug messages?
It isn't an official build. The Probekit agent.dll file which you sent me for EM64T was used (replacing the file from the build).When I use the EM64T build I will get an error even starting the probe insertion. However, I was under the impression the EM64T build has not been included as part of the download yet as that this defect was being used to track that inclusion. Have you included the EM64T build in the download?
Created attachment 70015 [details] ProbekitAgent debug build from Seva I am attaching the debug build Seva has sent. I will retry with this one today. I also have Joel testing the IPF build.
Seva, Thanks for sending the new debug version. Here is the output (note that the decode appears to be working but then ana error is thrown by the VM) [PROBEKIT MPICL_Instantiate] [PROBEKIT InitEC] [PROBEKIT EC Attach] [PROBEKIT EC Start] [PROBEKIT EC Start] [PROBEKIT Initialize BCI Instrumenter, options=ext-pk-BCILibraryName=BCIEngProbe] [PROBEKIT BCIEngine=BCIEngProbe] [PROBEKIT PROBEKIT_DATA_0=3srswAAAABVFbnRyeUV4aXQucHJvYmVzY3JpcHQAAAJZUkVNIE15UHJvYmUAAFBST0JFAABSRUYg T05FTlRSWSBFbnRyeUV4aXRfcHJvYmUkUHJvYmVfMCBfZW50cnkgKExqYXZhL2xhbmcvU3RyaW5nO0xqYXZhL2xhbmcvU3RyaW5nOylWIGNsYXNzTmFtZSxtZXRob2ROYW1lAABSRUYgT05FWElUIEVudHJ5RXhpdF9wcm9iZSRQcm9iZV8wIF9leGl0IChMamF2YS9sYW5nL1N0cmluZztMamF2YS9sYW5nL1N0cmluZzspViBjbGFzc05hbWUsbWV0aG9kTmFtZQAAUkVGIE9OQ0FUQ0ggRW50cnlFeGl0X3Byb2JlJFByb2JlXzAgX2NhdGNoIChMamF2YS9sYW5nL1Rocm93YWJsZTtMamF2YS9sYW5nL1N0cmluZztMamF2YS9sYW5nL1N0cmluZzspViBleGNlcHRpb25PYmplY3QsY2xhc3NOYW1lLG1ldGhvZE5hbWUAUlVMRSAgY29tIGlibSogKiAqIEVYQ0xVREUAUlVMRSAgY29tLmlibSogKiAqICogRVhDTFVERQBSVUxFICBjb20gc3VuKiAqICogRVhDTFVERQBSVUxFICBjb20uc3VuKiAqICogKiBFWENMVURFAEZJTFRFUiAgY29tIGlibSogKiAqIEVYQ0xVREUARklMVEVSICBjb20uaWJtKiAqICogKiBFWENMVURFAEZJTFRFUiAgY29tIHN1biogKiAqIEVYQ0xVREUARklMVEVSICBjb20uc3VuKiAqICogKiBFWENMVURFAAAAABVFbnRyeUV4aXRfcHJvYmUuY2xhc3MAAAFUyv66vgAAAC4AFAcAAgEAD0VudHJ5RXhpdF9wcm9iZQcABAEAEGphdmEvbGFuZy9PYmplY3QBAAY8aW5pdD4BAAMoKVYBAARDb2RlCgADAAkMAAUABgEAD0xpbmVOdW1iZXJUYWJsZQEAEkxvY2FsVmFyaWFibGVUYWJsZQEABHRoaXMBABFMRW50cnlFeGl0X3Byb2JlOwEAClNvdXJjZUZpbGUBABRFbnRyeUV4aXRfcHJvYmUuamF2YQEADElubmVyQ2xhc3NlcwcAEgEAF0VudHJ5RXhpdF9wcm9iZSRQcm9iZV8wAQAHUHJvYmVfMAAgAAEAAwAAAAAAAQAAAAUABgABAAcAAAAvAAEAAQAAAAUqtwAIsQAAAAIACgAAAAYAAQAAAAYACwAAAAwAAQAAAAUADAANAAAAAgAOAAAAAgAPABAAAAAKAAEAEQABABMACQAAAB1FbnRyeUV4aXRfcHJvYmUkUHJvYmVfMC5jbGFzcwAABl3K/rq+AAAALgBXBwACAQAXRW50cnlFeGl0X3Byb2JlJFByb2JlXzAHAAQBABBqYXZhL2xhbmcvT2JqZWN0AQAGc3BhY2VzAQASTGphdmEvbGFuZy9TdHJpbmc7AQAIPGNsaW5pdD4BAAMoKVYBAARDb2RlCAALAQAACQABAA0MAAUABgEAD0xpbmVOdW1iZXJUYWJsZQEAEkxvY2FsVmFyaWFibGVUYWJsZQEABjxpbml0PgoAAwASDAAQAAgBAAR0aGlzAQAZTEVudHJ5RXhpdF9wcm9iZSRQcm9iZV8wOwEABl9lbnRyeQEAJyhMamF2YS9sYW5nL1N0cmluZztMamF2YS9sYW5nL1N0cmluZzspVgkAGAAaBwAZAQAQamF2YS9sYW5nL1N5c3RlbQwAGwAcAQADb3V0AQAVTGphdmEvaW8vUHJpbnRTdHJlYW07BwAeAQAWamF2YS9sYW5nL1N0cmluZ0J1ZmZlcgoAIAAiBwAhAQAQamF2YS9sYW5nL1N0cmluZwwAIwAkAQAHdmFsdWVPZgEAJihMamF2YS9sYW5nL09iamVjdDspTGphdmEvbGFuZy9TdHJpbmc7CgAdACYMABAAJwEAFShMamF2YS9sYW5nL1N0cmluZzspVggAKQEACUVudGVyZWQ6IAoAHQArDAAsAC0BAAZhcHBlbmQBACwoTGphdmEvbGFuZy9TdHJpbmc7KUxqYXZhL2xhbmcvU3RyaW5nQnVmZmVyOwgALwEAAS4KAB0AMQwAMgAzAQAIdG9TdHJpbmcBABQoKUxqYXZhL2xhbmcvU3RyaW5nOwoANQA3BwA2AQATamF2YS9pby9QcmludFN0cmVhbQwAOAAnAQAHcHJpbnRsbggAOgEABCAgICABAAtteUNsYXNzTmFtZQEADG15TWV0aG9kTmFtZQEABV9leGl0CgAgAD8MAEAAQQEACXN1YnN0cmluZwEAFShJKUxqYXZhL2xhbmcvU3RyaW5nOwgAQwEACEV4aXRlZDogAQAGX2NhdGNoAQA8KExqYXZhL2xhbmcvVGhyb3dhYmxlO0xqYXZhL2xhbmcvU3RyaW5nO0xqYXZhL2xhbmcvU3RyaW5nOylWCABHAQADICEgCgADAEkMAEoASwEACGdldENsYXNzAQATKClMamF2YS9sYW5nL0NsYXNzOwoAHQBNDAAsAE4BACwoTGphdmEvbGFuZy9PYmplY3Q7KUxqYXZhL2xhbmcvU3RyaW5nQnVmZmVyOwEAEW15RXhjZXB0aW9uT2JqZWN0AQAVTGphdmEvbGFuZy9UaHJvd2FibGU7AQAKU291cmNlRmlsZQEAFEVudHJ5RXhpdF9wcm9iZS5qYXZhAQAMSW5uZXJDbGFzc2VzBwBVAQAPRW50cnlFeGl0X3Byb2JlAQAHUHJvYmVfMAAhAAEAAwAAAAEACQAFAAYAAAAFAAgABwAIAAEACQAAACoAAQAAAAAABhIKswAMsQAAAAIADgAAAAoAAgAAAAsABQAIAA8AAAACAAAAAQAQAAgAAQAJAAAALwABAAEAAAAFKrcAEbEAAAACAA4AAAAGAAEAAAAIAA8AAAAMAAEAAAAFABMAFAAAAAkAFQAWAAEACQAAAH4ABAACAAAAQrIAF7sAHVmyAAy4AB+3ACUSKLYAKiq2ACoSLrYAKiu2ACq2ADC2ADSyAAy7AB1aX7gAH7cAJRI5tgAqtgAwswAMsQAAAAIADgAAAA4AAwAAABIAKAATAEEAFQAPAAAAFgACAAAAQgA7AAYAAAAAAEIAPAAGAAEACQA9ABYAAQAJAAAAbwAEAAIAAAAzsgAMB7YAPrMADLIAF7sAHVmyAAy4AB+3ACUSQrYAKiq2ACoSLrYAKiu2ACq2ADC2ADSxAAAAAgAOAAAADgADAAAAHAAKAB0AMgAfAA8AAAAWAAIAAAAzADsABgAAAAAAMwA8AAYAAQAJAEQARQABAAkAAAByAAQAAwAAADCyABe7AB1ZsgAMuAAftwAlK7YAKhIutgAqLLYAKhJGtgAqKrYASLYATLYAMLYANLEAAAACAA4AAAAKAAIAAAAmAC8AKQAPAAAAIAADAAAAMABPAFAAAAAAADAAOwAGAAEAAAAwADwABgACAAIAUQAAAAIAUgBTAAAACgABAAEAVABWAAk=] [PROBEKIT total len = 3562] [PROBEKIT decoded 2669 bytes, magic=-557126464] [PROBEKIT nameLen=21 name = EntryExit.probescript dataLen = 601] [PROBEKIT content starts with REM MyProbe] [PROBEKIT probe script file processed successfully] [PROBEKIT nameLen=21 name = EntryExit_probe.class dataLen = 340] [PROBEKIT nameLen=29 name = EntryExit_probe$Probe_0.class dataLen = 1629] [PROBEKIT MPICL_Instantiate done] [PROBEKIT VM Init] [PROBEKIT CBCIInstrumenter::OnVMInit] [PROBEKIT process delayed class EntryExit_probe] [PROBEKIT DefineClass returned 00000000004FF7C0] [PROBEKIT process delayed class EntryExit_probe$Probe_0] [PROBEKIT DefineClass returned 00000000004FF7C8] [PROBEKIT instrumented java/lang/StringCoding] # # An unexpected error has been detected by HotSpot Virtual Machine: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000008237db4, pid=3324, tid=3412 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_06-b05 mixed mode) # Problematic frame: # V [jvm.dll+0x237db4] # # An error report file with more information is saved as hs_err_pid3324.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp
(In reply to comment #20) There is not enough information to spot the problem, and as I've mentioned before, I don't have a 64-bit windows machine. - try to debug it and at least find the traceback - do you really want to instrument java.lang.StringCoding ? Maybe start with a simple test case and your own classes? - does it work in standalone mode?
Created attachment 70028 [details] Error log form JVM Please find attached the detailed error log. It looks like a classLoader exception. I tried with a simple probe and got the same result. I will try to get it going in standalone.
Created attachment 70048 [details] Probes for remote testing access I am attaching probe files that I am using for standalone tests
After much testing, the current probekit build (May 31 candidate) is running on EM64T with IBM JREs. The above troubles were likely caused by defect 191000 to which I have added my results. I will test on IPF and report back.
I am not able to find an IBM 5.0 JRE for IPF. Can someone point me in the right direction?
Liz tested on EM64T. Testing on IPF remains if IBM 1.5 JRE available
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
