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.

"Killed" when building IPC with xdc tool

Hi all,

I am no longer able to rebuild IPC (using xdc).

I did it successfully quite recently to add a small change in the IPC code to fix an issue I found on our system (see http://e2e.ti.com/support/embedded/linux/f/354/p/263573/922868.aspx#922868 ).

I am using  TI_CGT_C6000_7.4.2, xdctools_3_24_07_73, ipc_1_25_02_12, bios_6_35_01_29

This is the sequence of commands I am using:

bash-4.1$ export 'XDCPATH=/vobs/rtools/ti_dsp/ipc/packages/;/vobs/rtools/ti_dsp/xdctools/packages;/vobs/rtools/ti_dsp/bios/packages/'
bash-4.1$ cd /vobs/rtools/ti_dsp/ipc/packages/ti/sdo/ipc/
bash-4.1$ /vobs/rtools/ti_dsp/xdctools/xdc
Killed
bash-4.1$

I get only that laconic "Killed" message.

I don't know what has changed between a few days ago (when this worked) and now.

How can I get more information on what's happening?

Note that I am building using xdc because I read about it in the "IPC Install Guide" (in the IPC 'docs' folder). But now I have seen that in the "IPC User Guide" (sprugo6e) it talks about building using make. Which one is the "correct" way (make or xdc)?

thanks

  • Some more information:

    1) The difference between "working" and "not working" is that is "not working" when I try it in a different directory (really it is a different clearcase view). I have copied all the tools (xdc, bios ,ipc) in the new directory and here I get the "Killed" message. In the old directory (clearcase view) it still works ok.

    2) I have looked inside the ipc.mak file and I can see that building using make (as suggested in the user guide) in the end just calls the xdc tool. (and for me generates the same 'Killed' outcome)

    3) It seems that the xdc proghram itself is the one that is killed. I have tried to run with gdb (I'm on Linux) and it seems to be killed at startup before reaching main :

    bash-4.1$ export 'XDCPATH=/vobs/rtools/ti_dsp/ipc/packages/;/vobs/rtools/ti_dsp/xdctools/packages;/vobs/rtools/ti_dsp/bios/packages/'
    bash-4.1$ cd /vobs/rtools/ti_dsp/ipc/packages/ti/sdo/ipc/
    bash-4.1$ gdb /vobs/rtools/ti_dsp/xdctools/xdc
    Copyright (C) 2010 Free Software Foundation, Inc.
    License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/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 "i686-redhat-linux-gnu".
    For bug reporting instructions, please see:
    <http://www.gnu.org/software/gdb/bugs/>...
    Reading symbols from /vobs/rtools/ti_dsp/xdctools_3_24_07_73/xdc...done.
    (gdb) b main
    Breakpoint 1 at 0x8048ff1
    (gdb) run
    Starting program: /vobs/rtools/ti_dsp/xdctools_3_24_07_73/xdc
    During startup program terminated with signal SIGKILL, Killed.
    (gdb)

    Who is the killer? Is the system killing it because XDC is doing something nasty at initialization (but before main?)

    Any hint on how to proceed to fix this issue will be greatly appreciated

    thanks

  • Hi Claudio,

    Can you try something basic like throwing the -help flag?  To see if it prints out the command's help contents?

    e.g. on our Linux system:

    1887 % $TOOLS/xdc/Linux/xdc -help
    usage: /db/toolsrc/library/tools/xdc/Linux/xdc [-h?|--help] [--help-make] [-k] [-n] [-r[a]] [def ...] [goal ...]
            [@opt-file] [-P[rRD] package-dir ...]

        -h, -?, --help - display this message and exit
        --help-make    - display GNU make command options
        -k             - don't stop on first build error (keep going)
        -n             - show the make command but don't execute it
        -r[a]          - (rebuild) use existing .xdcenv.mak to define XDC
                         environment variables XDCROOT and XDCPATH. If -ra
                         is specified, XDCARGS and XDCTARGETS are also read
                         from this file rather than from the environment.
        --xdcpath=path - set the XDCPATH to path.  This is identical to
                         passing the definition XDCPATH=path on the
                         command line.
        [def ...]      - def is a name=value pair that overrides the value
                         of the environent variable named name within the
                         this invocation of xdc
        [goal ...]     - goal is any valid GNU make command option or goal.
                         Common options and goals include:
                             .help    - display package-specific goals
                             all      - build all files
                             clean    - delete all generated files
                             test     - build and run all tests
                             release  - build all package release archives
        @opt-file      - treat all options contained in the file opt-file
                         as though they were directly inserted at the
                         location of this @ option.  This option may be
                         repeated anywhere the command line.  Each option
                         in opt-files must appear on a separate line and
                         contain only characters that should be part of
                         the option; no quote processing is done and all
                         space or tab characters are part of the option.
        -P[rRD] dir .. - build specified goal(s) in all directories
                         named after -P that contain a build script.
                         If -PD is specified, build the package based at
                         dir and (recursively) all other prerequisites of
                         this package.
                         If -Pr is specified, build all packages whose
                         repository is dir.
                         If -PR is specified, recursively descend into
                         specified directories and build every package that
                         contains a build script.

    Environment Variables
       XDCOPTIONS  options that affect output messages but never the
                   package bits actually generated include:
                       -d  debug makefile generation
                       -q  don't display any banners in recursive builds
                       -t  don't display date timestamps in banners
                       -v  show complete commands as they're executed
       XDCPATH     the user settable portion of the package path
       XDCARGS     arguments that are passed to the package's build
                   script, package.bld. The package's build script
                   references the arguments from the global array
                   arguments.
       XDCBUILDCFG if defined and the file './config.bld' does not exist,
                   this variable names a file that will be used in-lieu of
                   the config.bld file found along the package path.
       XDCTARGETS  a string of white space separated target names that
                   name the set of targets to build for, if the set is not
                   already specified by the config.bld file
    1888 %

    Steve

  • Steve,

    thank you for looking at this. I wasted all afternoon on this issue without any success.

    But the problem magically disappeared when the Linux build server was rebooted late in the afternoon.

    There was some unexplained screw up with the file system, so that executables might (or might not) be killed when started.

    Nothing to do with XDC tools at all.

    Sorry for having wasted time on the forum.