[SOLVED] Ozone loads elf file very slowly

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] Ozone loads elf file very slowly

    Hi there,

    i had a similar problem with ozone a year ago and it seems to have come back. Our embedded software uses c++ quite alot. Also with templates etc. There the symbol table is quite huge and the elf file has around 40MB. When i load the .elf file in ozone, it hangs for about 5min until it loads the elf file.
    The error message looks like this:

    ELF warning (1009): the symbol location decoder encountered an unsupported operand: DW_OP_GNU_convert.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0x0.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: DW_OP_GNU_const_type.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xFF.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: DW_OP_regval_type.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0x5.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0x4.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xF0.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: DW_OP_GNU_deref_type.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: DW_OP_convert.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xAB.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xAA.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xC6.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0x1.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xD1.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: DW_OP_constx.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xBD.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xB3.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0x7.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xDB.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: DW_OP_GNU_reinterpret.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xD0.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xCD.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xCC.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xD9.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xDE.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xAE.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xB7.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xC8.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: DW_OP_const_type.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xCA.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xB9.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xBE.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xD7.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xDA.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xBA.
    ELF warning (1009): the symbol location decoder encountered an unsupported operand: 0xF1.
    File.Open: completed in 272631 ms
    Edit.Preference (PREF_SHOW_ASM_CODE_PROFILE, 0);
    Edit.Preference (PREF_SHOW_SRC_CODE_PROFILE, 0);

    I currently use Ozone 2.60p in 64-Bit on Windows 10.

    Best,
    Hans

  • Hello Hans,

    Thank you for your inquiry.
    We received your inquiry via our Supportsystem as well.
    To avoid double information this thread will be closed now.

    Just a quick info to other readers. We were able to improve the load time in this case to around 15 s.
    The improved version should be available with the next Ozone release V2.62.

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.