[ABANDONED] JLinkDebugger crashes loading .elf file

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

  • [ABANDONED] JLinkDebugger crashes loading .elf file

    Hi

    I have a problem with loading an .elf file. The Debugger crashes while loading the .elf, caused by a buffer overflow. This error occurs using the version 1.78 on Windows, 1.79a 64Bit on Windows and 1.79a 64Bit on Linux. The .elf file is about 3.3MB of size and is compiled with GCC 4.8 for embedded arm. Another .elf file using the same compiler (and the same compiler flags as far as I'm aware) does work just fine. That file is only 2.1MB in size.

    If you want to have a look at the .elf file (as I assume you do), I have to get a release for it by my supervisors because it's proprietary code. And I can send it only by private ways, posting it here won't be possible.

    To start with, I can provide the following callstacks from both windows and linux:

    Callstack Windows:

    > msvcr100.dll!00000000647e4930() Unknown
    J-Link Debugger.exe!000000013fdafd6a() Unknown
    J-Link Debugger.exe!000000013fd9c8e8() Unknown
    J-Link Debugger.exe!000000013fda22c8() Unknown
    J-Link Debugger.exe!000000013fda2e55() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2f4e() Unknown
    J-Link Debugger.exe!000000013fda2f4e() Unknown
    J-Link Debugger.exe!000000013fda2f4e() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    ...
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2fe7() Unknown
    J-Link Debugger.exe!000000013fda2f4e() Unknown
    J-Link Debugger.exe!000000013fda3473() Unknown
    J-Link Debugger.exe!000000013fda498d() Unknown
    J-Link Debugger.exe!000000013fda4d02() Unknown
    J-Link Debugger.exe!000000013fd71ce3() Unknown
    J-Link Debugger.exe!000000013fcbb74a() Unknown
    J-Link Debugger.exe!000000013fcbe8f6() Unknown
    J-Link Debugger.exe!000000013fcba7e4() Unknown
    QtCore4.dll!0000000064909972() Unknown
    QtCore4.dll!0000000064918567() Unknown
    msvcr100.dll!0000000064791d9f() Unknown
    msvcr100.dll!0000000064791e3b() Unknown
    kernel32.dll!000000007754652d() Unknown
    ntdll.dll!000000007767c521() Unknown


    Callstack Linux:

    *** buffer overflow detected ***: ./JLinkDebugger terminated
    ======= Backtrace: =========
    /lib64/libc.so.6(+0x712df)[0x7fb476c642df]
    /lib64/libc.so.6(__fortify_fail+0x37)[0x7fb476ce9e17]
    /lib64/libc.so.6(+0xf4f90)[0x7fb476ce7f90]
    /lib64/libc.so.6(+0xf40eb)[0x7fb476ce70eb]
    ./JLinkDebugger[0x61ac10]
    ./JLinkDebugger[0x61b068]
    ./JLinkDebugger[0x61b22a]
    ./JLinkDebugger[0x6184f7]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x618589]
    ./JLinkDebugger[0x618589]
    ./JLinkDebugger[0x618589]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]
    ...
    ./JLinkDebugger[0x6185dd]
    ./JLinkDebugger[0x6185dd]

  • Hi Matt,

    thanks for your inquiry.
    If you want to have a look at the .elf file (as I assume you do), I have to get a release for it by my supervisors because it's proprietary code. And I can send it only by private ways, posting it here won't be possible.

    Having a chance to take a look at the elf-file would definitely be very helpful.
    Could you try to narrow down the code causing the "problematic" elf-section by excluding module after module from the build and rechecking if the problem occurs?
    This way, it would maybe sufficient to send a smaller .elf file that contains much less proprietary code.


    Best regards,
    Niklas
    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.