This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCSv5.0.2 (linux) crash on connect to target

In case it makes a difference, this is on a 64bit ubuntu 10.10 running on my laptop..

About 9 times out of 10 it crashes.  At some point in the past it would only crash if I tried to connect to target running off battery, but would be fine if laptop was running off charger.  So I guess this is could be a race condition.

here are my dslog.txt and java crash log

0116.logs.zip

backtrace from java crash log is:

Stack: [0xc30f2000,0xc3173000),  sp=0xc3170eac,  free space=507k

Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)

C  [libjscserdesv2.so+0x23932]  usb_destroy_configuration+0xfa

C  [libjscserdesv2.so+0x22c6c]  usb_free_dev+0x10

C  [libjscserdesv2.so+0x22e11]  usb_find_devices+0x189

C  [libjscserdesv2.so+0x2003f]  ftdi_usb_open_desc_index+0x36

C  [libjscserdesv2.so+0x205c6]  ftdi_usb_open_string+0x2ff

C  [libjscserdesv2.so+0x1eec7]  _Z7ft_openPc14ftdi_interfacePP14FT_INFO_STRUCT+0xb9

C  [libjscserdesv2.so+0x1ece4]  FT_Open+0x7c

C  [libjscserdesv2.so+0xf764]  _Z8FtdiOpenP10JSC_Inform+0x140

C  [libjscserdesv2.so+0x14075]

C  [libjscserdesv2.so+0x133d3]  _Z14jsc_InitHandleP10JSC_Informj10JTI_ClientP13CFG_InterfacePv+0xd3

C  [libjscserdesv2.so+0x15fca]  JSC_CreateHandle+0x5e

C  [libxdsfast3.so+0x1a737]  _Z16jsc_CreateHandlePvPS_P13JSC_Parameter+0x6b

C  [libxdsfast3.so+0x1a2cf]  _Z10jsc_CreatePKcPPvPP13JSC_InterfaceS2_P13JSC_Parameterb+0xa3

C  [libxdsfast3.so+0x2b7ab]

C  [libxdsfast3.so+0x2b09b]

C  [libxdsfast3.so+0x2a397]  _Z14smg_InitHandlePv10JTI_ClientPcjPb+0x293

C  [libxdsfast3.so+0x31f52]  SMG_open+0x242

C  [libtixds510icepick_d.so+0x3be3]  PTI_EmuInitScan+0xfb

C  [libtixds510icepick_d.so+0x5a17]  PTI_connect+0x8d

C  [libtixds510icepick_d.so+0xb304]  TRG_connect+0xd5

C  [libtixds510icepick_d.so+0x8bfd]  GTI_CONNECT+0x7c

C  [libDebugServer.so+0x3a9acb]  _ZN7UID_GTI13DriverConnectEv+0x67

C  [libDebugServer.so+0x3bd57c]  _ZN7UID_GTI4PollEv+0x11b8

C  [libDebugServer.so+0x3622ea]  _ZN22SafeListenerConnectionI9IPollableE15ForEachListenerERK30SafeListenerConnectionCallbackIS0_E+0x4e

C  [libDebugServer.so+0x361f08]  _ZN15DspEventManager4PollEv+0x1c

C  [libDebugServer.so+0x35f1f2]  _ZN10dsDebugger4PollEPj+0x96

C  [libxul.so+0x199fe9]  XPTC_InvokeByIndex+0x29

C  [libxul.so+0x1f6677]  Java_org_mozilla_xpcom_internal_XPCOMJavaProxy_callXPCOMMethod+0x729

J  org.mozilla.xpcom.internal.XPCOMJavaProxy.callXPCOMMethod(Ljava/lang/Object;Ljava/lang/String;[Ljava/lang/Object;Ljava/lang/String;)Ljava/lang/Object;

J  org.mozilla.xpcom.internal.XPCOMJavaProxy$3.call()Ljava/lang/Object;

J  org.mozilla.xpcom.internal.XPCOMImpl$XPCOMCallExecutor.submit(Ljava/util/concurrent/Callable;)Ljava/lang/Object;

J  org.mozilla.xpcom.internal.XPCOMJavaProxy.invoke(Ljava/lang/Object;Ljava/lang/reflect/Method;[Ljava/lang/Object;)Ljava/lang/Object;

j  $Proxy4.poll()J+9

j  com.ti.debug.engine.impl.Application.poll()J+11

j  com.ti.debug.engine.cce.CCEDebugEngine$PollingThread.run()V+141

v  ~StubRoutines::call_stub

V  [libjvm.so+0x17b2bc]

 

  • Hi,

    A first glance to the <dslog.txt> shows it abruptly ends, indicating the issue caught the debug server unprepared and therefore its origin is outside of the debug server itself. 

    I couldn't spot any issues with the JVM dump as well, as I couldn't find any invalid paths or excessive memory usage. 

    It seems you are debugging OMAP4 with a XDS100v2, is that so? If so, I've also used this configuration (OMAP4, XDS100, Ubuntu 10.04 64bits) but on a Desktop. I haven't tried to run the board off of batteries, though. 

    Please confirm the system setup and I can try to get a reproducible test case here, ok?

    Thanks,

    Rafael

     

  • Hi Rafael,

    yup, omap4 w/ xds100v2

    I think the battery vs wall power was, at some point, just changing the timing slightly (rather than being a true root cause)..  I guess the main difference from your setup is ubuntu 10.10 vs 10.04.

    Anyways, if you have anything you want me to try to debug, then let me know.  I brought my xds100v2 in with me today, and can reproduce the problem pretty easily.

     

    BR,

    -R

  • fyi, I'm still getting a similar crash w/ CCSv5.1M7:

     

    Stack: [0xc424f000,0xc42a0000],  sp=0xc429dee0,  free space=315k
    Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
    C  [libc.so.6+0x7288e]  cfree+0x2e
    C  [libjscserdesv2.so+0x23bfc]  usb_free_dev+0x10
    C  [libjscserdesv2.so+0x23da1]  usb_find_devices+0x189
    C  [libjscserdesv2.so+0x20fcf]  ftdi_usb_open_desc_index+0x36
    C  [libjscserdesv2.so+0x21556]  ftdi_usb_open_string+0x2ff
    C  [libjscserdesv2.so+0x1fe57]  _Z7ft_openPc14ftdi_interfacePP14FT_INFO_STRUCT+0xb9
    C  [libjscserdesv2.so+0x1fc74]  FT_Open+0x7c
    C  [libjscserdesv2.so+0xff5c]  _Z8FtdiOpenP10JSC_Inform+0x140
    C  [libjscserdesv2.so+0x148c9]
    C  [libjscserdesv2.so+0x13c27]  _Z14jsc_InitHandleP10JSC_Informj10JTI_ClientP13CFG_InterfacePv+0xd3
    C  [libjscserdesv2.so+0x1685a]  JSC_CreateHandle+0x5e
    C  [libxdsfast3.so+0x19f93]  _Z16jsc_CreateHandlePvPS_P13JSC_Parameter+0x6b
    C  [libxdsfast3.so+0x19b2b]  _Z10jsc_CreatePKcPPvPP13JSC_InterfaceS2_P13JSC_Parameterb+0xa3
    C  [libxdsfast3.so+0x2b8c5]
    C  [libxdsfast3.so+0x2b1db]
    C  [libxdsfast3.so+0x2a4d7]  _Z14smg_InitHandlePv10JTI_ClientPcjPb+0x293
    C  [libxdsfast3.so+0x3206a]  SMG_open+0x242
    C  [libtixds510icepick_d.so+0x3c93]  PTI_EmuInitScan+0xfb
    C  [libtixds510icepick_d.so+0x5ac7]  PTI_connect+0x8d
    C  [libtixds510icepick_d.so+0xb82a]  TRG_connect+0xd5
    C  [libtixds510icepick_d.so+0x9119]  GTI_CONNECT+0x7c
    C  [libDebugServer.so+0x3b84c7]  _ZN7UID_GTI13DriverConnectEv+0x67
    C  [libDebugServer.so+0x3c958c]  _ZN7UID_GTI16LogicallyConnectEv+0x2c
    C  [libDebugServer.so+0x3d1884]  _ZN7UID_GTI4PollEv+0x274
    C  [libDebugServer.so+0x3817c0]  _ZN15DspEventManager4PollEv+0x40
    C  [libDebugServer.so+0x3595a1]  _ZN10dsDebugger6DoPollEb+0xa1
    C  [libDebugServer.so+0x359665]  _ZN10dsDebugger14PollThreadMainEPj+0x25
    C  [libxul.so+0xb0ca8b]  NS_InvokeByIndex_P+0x2f
    C  [libxul.so+0xb4c465]  Java_org_mozilla_xpcom_internal_XPCOMJavaProxy_callXPCOMMethod+0x4d9
    j  org.mozilla.xpcom.internal.XPCOMJavaProxy.callXPCOMMethod(Ljava/lang/Object;Ljava/lang/String;[Ljava/lang/Object;)Ljava/lang/Object;+0
    j  org.mozilla.xpcom.internal.XPCOMJavaProxy.invoke(Ljava/lang/Object;Ljava/lang/reflect/Method;[Ljava/lang/Object;)Ljava/lang/Object;+198

  • well, I tried it again after upgrading to 5.1.0.09000 (and ubuntu 11.10), and now I don't see this issue..