• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 56 subscribers
  • Views 3116 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/CCSTUDIO: Segmentation fault

Eugene S
Prodigy 10 points
Part Number: CCSTUDIO

Tool/software: Code Composer Studio

Hello,

I have problem with running CCSv6 on Ubuntu. It seems that was happen after OS update 20.06.2017.

There is log from terminal:

eugene@PC:~/ti/ccsv6/eclipse$ ./ccstudio
Segmentation fault (core dumped)

with gdb:

(gdb) run
Starting program: /home/eugene/ti/ccsv6/eclipse/ccstudio
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
process 8605 is executing new program: /home/eugene/ti/ccsv6/eclipse/ccstudio
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0xb60ea15b in _expand_stack_to(unsigned char*) () from /home/eugene/ti/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
(gdb) bt
#0  0xb60ea15b in _expand_stack_to(unsigned char*) () from /home/eugene/ti/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
#1  0xb60ea1f9 in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () from /home/eugene/ti/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
#2  0xb60ee2f3 in os::create_attached_thread(JavaThread*) () from /home/eugene/ti/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
#3  0xb61bc86b in Threads::create_vm(JavaVMInitArgs*, bool*) () from /home/eugene/ti/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
#4  0xb5fccb3c in JNI_CreateJavaVM () from /home/eugene/ti/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
#5  0xb7fd222a in startJavaJNI (libPath=0x805b980 "/home/eugene/ti/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so", vmArgs=0x80eb7c0, progArgs=0x80ea2c8,
    jarFile=0x805e470 "/home/eugene/ti/ccsv6/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar") at ../eclipseJNI.c:358
#6  0xb7fd3898 in startJavaVM (libPath=0x805b980 "/home/eugene/ti/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so", vmArgs=0x80eb7c0, progArgs=0x80ea2c8,
    jarFile=0x805e470 "/home/eugene/ti/ccsv6/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar") at ../eclipseNix.c:174
#7  0xb7fcd1f6 in _run (argc=3, argv=0x804f8d0, vmArgs=0x80673c8) at ../eclipse.c:629
#8  0xb7fccc03 in run (argc=3, argv=0x804f8d0, vmArgs=0x8050280) at ../eclipse.c:465
#9  0x080497a9 in main (argc=14, argv=0x804f8d0) at ../eclipseMain.c:332

  • 0
    Prodigy 40 points
    Same issue here (on kubuntu 17.04), yesterday it was working, today segmentation fault (I was using 7.0.x version and same happens with latest 7.2.x)
  • 0 in reply to blaxter
    Prodigy 40 points

    It seems the issue is with latest kernel, this was the update that broke everything:

    Start-Date: 2017-06-21  07:48:38
Commandline: /usr/bin/unattended-upgrade
Install: linux-image-4.10.0-24-generic:amd64 (4.10.0-24.28, automatic), linux-signed-image-4.10.0-24-generic:amd64 (4.10.0-24.28, automatic), linux-image-extra-4.10.0-24-generic:amd64 (4.10.0-24.28, automatic), linux-headers-4.10.0-24:a
md64 (4.10.0-24.28, automatic), linux-headers-4.10.0-24-generic:amd64 (4.10.0-24.28, automatic)
Upgrade: linux-headers-generic:amd64 (4.10.0.22.24, 4.10.0.24.26), linux-libc-dev:amd64 (4.10.0-22.24, 4.10.0-24.28), libc6-dbg:amd64 (2.24-9ubuntu2, 2.24-9ubuntu2.2), libc6-dev:amd64 (2.24-9ubuntu2, 2.24-9ubuntu2.2), linux-image-generi
c:amd64 (4.10.0.22.24, 4.10.0.24.26), linux-signed-image-generic:amd64 (4.10.0.22.24, 4.10.0.24.26), libc6:amd64 (2.24-9ubuntu2, 2.24-9ubuntu2.2), libc6:i386 (2.24-9ubuntu2, 2.24-9ubuntu2.2), locales:amd64 (2.24-9ubuntu2, 2.24-9ubuntu2.
2), linux-signed-generic:amd64 (4.10.0.22.24, 4.10.0.24.26), libc-bin:amd64 (2.24-9ubuntu2, 2.24-9ubuntu2.2), libc6-i386:amd64 (2.24-9ubuntu2, 2.24-9ubuntu2.2), libc-dev-bin:amd64 (2.24-9ubuntu2, 2.24-9ubuntu2.2), multiarch-support:amd6
4 (2.24-9ubuntu2, 2.24-9ubuntu2.2), linux-generic:amd64 (4.10.0.22.24, 4.10.0.24.26)

    At first I thought the issue could be because of the update of libc-bin libc-dev-bin libc6 libc6:i386 libc6-dbg libc6-dev libc6-i386 locales multiarch-support packages from 2.24-9ubuntu2 to 2.24-9ubuntu2.2 but it's not. The issue is with the latest kernel installed there, I went back to 4.10.0-22-generic #24-Ubuntu and it's working again (temporal workaround though not ideal).

  • 0 in reply to blaxter
    Prodigy 130 points
    Could you give more info on how to change the kernel? I reinstalled the Ubuntu, hence downgrading to previous version is not an option for me now. Thanks in advance.
  • 0 in reply to Kivanc Kabasakal
    Prodigy 40 points
    If you are using defaults, you should have grub2 installed and when you start your pc there is a second option "advanced something soimething" and then you can choose previous versions of the kernel
  • 0 in reply to blaxter
    TI__Guru**** 441491 points
    Hello,
    This is a known issue that is under priority investigation:
    e2e.ti.com/.../604599

    Thanks
    ki
  • 0 in reply to Ki
    Prodigy 40 points
    I get the same core dump while running ccsV6 on kubuntu 16.10 via virtual box.
    Started happening today after I rebooted my Vbox VM.

    When running with gdb, i get the following stack trace:

    [jchiang@jchiang-VirtualBox:bash-4.3:eclipse]> gdb ./ccstudio
    GNU gdb (Ubuntu 7.11.90.20161005-0ubuntu1) 7.11.90.20161005-git
    Copyright (C) 2016 Free Software Foundation, Inc.
    License GPLv3+: GNU GPL version 3 or later <gnu.org/.../gpl.html>
    This is free software: you are free to change and redistribute it.
    There is NO WARRANTY, to the extent permitted by law. Type "show copying"
    and "show warranty" for details.
    This GDB was configured as "x86_64-linux-gnu".
    Type "show configuration" for configuration details.
    For bug reporting instructions, please see:
    <www.gnu.org/.../>.
    Find the GDB manual and other documentation resources online at:
    <www.gnu.org/.../>.
    For help, type "help".
    Type "apropos word" to search for commands related to "word"...
    Reading symbols from ./ccstudio...done.
    (gdb) run
    Starting program: /home/jchiang/ti_ORIG/ccsv6/eclipse/ccstudio
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
    process 13359 is executing new program: /home/jchiang/ti_ORIG/ccsv6/eclipse/ccstudio
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

    (ccstudio:13359): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",

    (ccstudio:13359): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",

    Program received signal SIGSEGV, Segmentation fault.
    0xf5fea15b in _expand_stack_to(unsigned char*) () from /home/jchiang/ti_ORIG/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
    (gdb) bt
    #0 0xf5fea15b in _expand_stack_to(unsigned char*) () from /home/jchiang/ti_ORIG/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
    #1 0xf5fea1f9 in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () from /home/jchiang/ti_ORIG/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
    #2 0xf5fee2f3 in os::create_attached_thread(JavaThread*) () from /home/jchiang/ti_ORIG/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
    #3 0xf60bc86b in Threads::create_vm(JavaVMInitArgs*, bool*) () from /home/jchiang/ti_ORIG/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
    #4 0xf5eccb3c in JNI_CreateJavaVM () from /home/jchiang/ti_ORIG/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
    #5 0xf7fc822a in startJavaJNI (libPath=0x805f5f0 "/home/jchiang/ti_ORIG/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so", vmArgs=0x8099c58, progArgs=0x80eceb0,
    jarFile=0x805ee98 "/home/jchiang/ti_ORIG/ccsv6/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar") at ../eclipseJNI.c:358
    #6 0xf7fc9898 in startJavaVM (libPath=0x805f5f0 "/home/jchiang/ti_ORIG/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so", vmArgs=0x8099c58, progArgs=0x80eceb0,
    jarFile=0x805ee98 "/home/jchiang/ti_ORIG/ccsv6/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar") at ../eclipseNix.c:174
    #7 0xf7fc31f6 in _run (argc=3, argv=0x804f8a8, vmArgs=0x805c3c0) at ../eclipse.c:629
    #8 0xf7fc2c03 in run (argc=3, argv=0x804f8a8, vmArgs=0x8050250) at ../eclipse.c:465
    #9 0x080497a9 in main (argc=14, argv=0x804f8a8) at ../eclipseMain.c:332
    (gdb)

    I don't believe I updated my linux kernel but something must have changed.

    Any help would be appreciated.
  • 0 in reply to Ki
    Prodigy 40 points
    Same thing happened to me today after rebooting my kubuntu virtual machine.
    I don't believe I did any kernel updates. I'm running kubuntu 16.10 via virtual box from a windows laptop.

    This is the backtrace I get when running ccstudio via gdb:

    [jchiang@jchiang-VirtualBox:bash-4.3:eclipse]> gdb ./ccstudio
    GNU gdb (Ubuntu 7.11.90.20161005-0ubuntu1) 7.11.90.20161005-git
    Copyright (C) 2016 Free Software Foundation, Inc.
    License GPLv3+: GNU GPL version 3 or later <gnu.org/.../gpl.html>
    This is free software: you are free to change and redistribute it.
    There is NO WARRANTY, to the extent permitted by law. Type "show copying"
    and "show warranty" for details.
    This GDB was configured as "x86_64-linux-gnu".
    Type "show configuration" for configuration details.
    For bug reporting instructions, please see:
    <www.gnu.org/.../>.
    Find the GDB manual and other documentation resources online at:
    <www.gnu.org/.../>.
    For help, type "help".
    Type "apropos word" to search for commands related to "word"...
    Reading symbols from ./ccstudio...done.
    (gdb) run
    Starting program: /home/jchiang/ti_ORIG/ccsv6/eclipse/ccstudio
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
    process 13359 is executing new program: /home/jchiang/ti_ORIG/ccsv6/eclipse/ccstudio
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

    (ccstudio:13359): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",

    (ccstudio:13359): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",

    Program received signal SIGSEGV, Segmentation fault.
    0xf5fea15b in _expand_stack_to(unsigned char*) () from /home/jchiang/ti_ORIG/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
    (gdb) bt
    #0 0xf5fea15b in _expand_stack_to(unsigned char*) () from /home/jchiang/ti_ORIG/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
    #1 0xf5fea1f9 in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () from /home/jchiang/ti_ORIG/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
    #2 0xf5fee2f3 in os::create_attached_thread(JavaThread*) () from /home/jchiang/ti_ORIG/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
    #3 0xf60bc86b in Threads::create_vm(JavaVMInitArgs*, bool*) () from /home/jchiang/ti_ORIG/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
    #4 0xf5eccb3c in JNI_CreateJavaVM () from /home/jchiang/ti_ORIG/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so
    #5 0xf7fc822a in startJavaJNI (libPath=0x805f5f0 "/home/jchiang/ti_ORIG/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so", vmArgs=0x8099c58, progArgs=0x80eceb0,
    jarFile=0x805ee98 "/home/jchiang/ti_ORIG/ccsv6/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar") at ../eclipseJNI.c:358
    #6 0xf7fc9898 in startJavaVM (libPath=0x805f5f0 "/home/jchiang/ti_ORIG/ccsv6/eclipse/jre/bin/../lib/i386/client/libjvm.so", vmArgs=0x8099c58, progArgs=0x80eceb0,
    jarFile=0x805ee98 "/home/jchiang/ti_ORIG/ccsv6/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar") at ../eclipseNix.c:174
    #7 0xf7fc31f6 in _run (argc=3, argv=0x804f8a8, vmArgs=0x805c3c0) at ../eclipse.c:629
    #8 0xf7fc2c03 in run (argc=3, argv=0x804f8a8, vmArgs=0x8050250) at ../eclipse.c:465
    #9 0x080497a9 in main (argc=14, argv=0x804f8a8) at ../eclipseMain.c:332
    (gdb)


    Any help on this would be appreciated.

    thanks.
  • 0 in reply to Joe Chiang47
    Prodigy 40 points
    uname -a, you are most likely using 4.10.0-24
  • 0 in reply to blaxter
    Prodigy 40 points

    I'm running

    Linux jchiang-VirtualBox 4.8.0-56-generic #61-Ubuntu SMP Wed Jun 14 08:15:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  • 0 in reply to Joe Chiang47
    Prodigy 40 points

    I looked at /var/log/apt/history.log and saw this update that coincided with the time ccstudio started failing:

    Start-Date: 2017-06-20 03:16:05
    Commandline: /usr/bin/unattended-upgrade
    Install: linux-headers-4.8.0-56:amd64 (4.8.0-56.61, automatic), linux-image-4.8.0-56-generic:amd64 (4.8.0-56.61, automatic), linux-image-extra-4.8.0-56-generic:amd64 (4.8.0-56.61, automatic), linux-headers-4.8.0-56-generic:amd64 (4.8.0-56.61, automatic)
    Upgrade: linux-headers-generic:amd64 (4.8.0.54.66, 4.8.0.56.69), libc6-dev-x32:amd64 (2.24-3ubuntu2, 2.24-3ubuntu2.2), linux-libc-dev:amd64 (4.8.0-54.57, 4.8.0-56.61), linux-libc-dev:i386 (4.8.0-54.57, 4.8.0-56.61), libc6-dev-i386:amd64 (2.24-3ubuntu2, 2.24-3ubuntu2.2), libc6-dbg:amd64 (2.24-3ubuntu2, 2.24-3ubuntu2.2), libc6-dev:amd64 (2.24-3ubuntu2, 2.24-3ubuntu2.2), libc6-dev:i386 (2.24-3ubuntu2, 2.24-3ubuntu2.2), linux-image-generic:amd64 (4.8.0.54.66, 4.8.0.56.69), libc6:amd64 (2.24-3ubuntu2, 2.24-3ubuntu2.2), libc6:i386 (2.24-3ubuntu2, 2.24-3ubuntu2.2), locales:amd64 (2.24-3ubuntu2, 2.24-3ubuntu2.2), libc-bin:amd64 (2.24-3ubuntu2, 2.24-3ubuntu2.2), libc6-x32:amd64 (2.24-3ubuntu2, 2.24-3ubuntu2.2), libc6-i386:amd64 (2.24-3ubuntu2, 2.24-3ubuntu2.2), libc-dev-bin:amd64 (2.24-3ubuntu2, 2.24-3ubuntu2.2), multiarch-support:amd64 (2.24-3ubuntu2, 2.24-3ubuntu2.2), linux-generic:amd64 (4.8.0.54.66, 4.8.0.56.69)
    End-Date: 2017-06-20 03:17:32

    Is there a way to roll back this update?

  • 0 in reply to Joe Chiang47
    TI__Guru**** 441491 points
    Hello,
    Note that the latest Linux kernel update appears to have a fix for the issue. If you are still hitting this issue, make sure you have the latest kernel updates installed.

    e2e.ti.com/.../604599

    Thanks
    ki