SCM command line core dump
I am attempting to invoke SCM actions via command line but the tool fails with a core dump. Any thoughts?
Brian > scm -v Unhandled exception Type=Segmentation error vmState=0x00040000 J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000001 Handler1=F7D090A4 Handler2=F7CCE854 InaccessibleAddress=00000004 EDI=00000000 ESI=0804C8A8 EAX=0804C8A8 EBX=FFFFD0B4 ECX=F7FDBADC EDX=0804C8A8 EIP=F7D4E497 ES=0000002B DS=0000002B ESP=FFFFD020 EFlags=00210282 CS=FFFF0023 SS=0000002B EBP=FFFFD038 Module=/myserver/app/team/jazz/client/eclipse/jdk/jre/bin/libj9thr23.so Module_base_address=F7D4A000 Target=2_30_20080314_17962_lHdSMr (Linux 2.6.9-78.0.1.ELsmp) CPU=x86 (8 logical CPUs) (0xfbb9a6000 RAM) JVMDUMP006I Processing Dump Event "gpf", detail "" - Please Wait. JVMDUMP007I JVM Requesting System Dump using '/myserver/app/team/jazz/client/eclipse/core.20090812.161155.22225.0001.dmp' JVMDUMP010I System Dump written to /myserver/app/team/jazz/client/eclipse/core.20090812.161155.22225.0001.dmp JVMDUMP007I JVM Requesting Snap Dump using '/myserver/app/team/jazz/client/eclipse/Snap.20090812.161155.22225.0002.trc' JVMDUMP010I Snap Dump written to /myserver/app/team/jazz/client/eclipse/Snap.20090812.161155.22225.0002.trc JVMDUMP007I JVM Requesting Java Dump using '/myserver/app/team/jazz/client/eclipse/javacore.20090812.161155.22225.0003.txt' JVMDUMP010I Java Dump written to /myserver/app/team/jazz/client/eclipse/javacore.20090812.161155.22225.0003.txt JVMDUMP013I Processed Dump Event "gpf", detail "". |
3 answers
I am attempting to invoke SCM actions via command line but the tool fails with a core dump. Any thoughts? Nothing springs to mind. Can you file an RTC bug against "Source Control/Client Library/CLI"? Please include your OS and client version. In the mean time, try switching VMs. You can do that by editing 'scm.ini', and changing the line below '-vm' to the path of some different binary. e |
|
Found something interesting.
When I execute the tool from the directory in which it is installed, it appears to run successfully. Running it from anywhere else results in the core dump. Does that make any sense? This is running on a Linux instance. Thanks, Brian com.ibm.team.filesystem.cli.tools, version 0.6.0.M200805202108 Subcommands: tools.verify com.ibm.team.filesystem.cli.client, version 0.6.0.M200812041253 Subcommands: load login logout create create/workspace create/baseline create/changeset changeset changeset/comment changeset/close changeset/relocate changeset/associate changeset/disassociate daemon daemon/start daemon/stop change-target change-target/workspace change-target/component list list/workspaces list/projectareas list/teamareas list/streams list/contributors list/components list/remotefiles list/credentials checkin accept deliver status conflicts resolve move lastmod share discard undo history diff repair com.ibm.team.filesystem.cli.core, version 0.6.0.M200811071624 Subcommands: help version |
|
That looks like a M1 or M2 version of 2.0. I suggest upgrading to a newer client.
It sounds like the CLI isn't picking up the Java binary. If you edit the scm.ini and change the line below '-vm' to an absolute path that points to a java binary, does it work? If you download a newer client (both CLI and eclipse workbench) and try running that, does it work? I suspect that your older CLI may have issues that were fixed recently. e |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.