Hot!XC16 - v1.32B - elf-objdump.exe has stopped working

Author
dennisnguy
Starting Member
  • Total Posts : 72
  • Reward points : 0
  • Joined: 2013/08/30 09:19:51
  • Location: 0
  • Status: offline
2017/09/01 07:39:15 (permalink)
0

XC16 - v1.32B - elf-objdump.exe has stopped working

Hi Everyone,
 
I got the "elf-objdump.exe has stopped working" error message with XC16 - v1.32B (note: there is no issue with XC16 v1.31, v1.30, v1.26)
I'm using MLAB XIDE v4.0, windows 7 version 6.1.
Here is problem details:
Problem signature:
Problem Event Name: APPCRASH
Application Name: elf-objdump.exe
Application Version: 0.0.0.0
Application Timestamp: 59931408
Fault Module Name: elf-objdump.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 59931408
Exception Code: c0000005
Exception Offset: 0000394e
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
 
Please let me know how to fix the elf-objdump.exe error.
 
Thanks in advance!
#1

4 Replies Related Threads

    alex.davies
    New Member
    • Total Posts : 4
    • Reward points : 0
    • Joined: 2014/08/31 21:37:02
    • Location: 0
    • Status: offline
    Re: XC16 - v1.32B - elf-objdump.exe has stopped working 2017/09/15 20:05:07 (permalink)
    0
    Getting this error very regularly. Inside of MPLAB, I get error #255 and it generates no hex/map, running the compiler outside of MPLAB I get "stopped working" but at least it generates a hex/map.
    #2
    RISC
    Super Member
    • Total Posts : 4480
    • Reward points : 0
    • Status: offline
    Re: XC16 - v1.32B - elf-objdump.exe has stopped working 2017/09/16 04:54:37 (permalink)
    +1 (1)
    Hi,
    You should report this through a ticket to Microchip if you want to get this fixed in a future version.
    This is a user forum.
    Regards
     
    #3
    cawilkie
    Administrator
    • Total Posts : 1959
    • Reward points : 0
    • Joined: 2003/11/07 12:49:11
    • Status: offline
    Re: XC16 - v1.32B - elf-objdump.exe has stopped working 2017/09/16 09:57:06 (permalink)
    +2 (2)
    Hi all,
     
       We have recently discovered this issue with objdump crashing after the build and are aware of it.  I received some reports on Wednesday and have identified the cause and the resolution.  That doesn't really help users out there today!
     
       The issue is that there are some data sections in FLASH (typically space(prog) or 'code' assembly sections that contain data) that look like code sections and the checker tool is trying to evaluate the code (only for EP devices).  Unfortunately this fails in a dramatic way.
     
       The good new is that at this point the compiler and linker have finished there work, and an ELF file is sitting where it ought to sit (doing a further build - not clean and build) should allow MPLAB X to find it and program the device.  The bad news is that the checker tool is not able to check the safety of this code.
     
       We got off schedule with releases and are planning a quick-turn release for v1.33 which will be another part-support release with a number of bug fixes, including this one.
     
       If you have any further questions about this issue, please send me a private message and will be happy to respond.
     
    Regards
    Calum
    #4
    Jack_M
    Senior Member
    • Total Posts : 126
    • Reward points : 0
    • Joined: 2012/11/17 06:27:45
    • Location: 0
    • Status: offline
    Re: XC16 - v1.32B - elf-objdump.exe has stopped working 2017/10/13 00:37:06 (permalink)
    0
    Hi Calum,
    i just discovered this error, too.
    I am writing code for dsPIC33EV256GM106
    doing this
    volatile const __attribute__((space(prog),address(0x200))) uint16_t reserved_space[256]

    to reserve some space (for a bootloader)
     
    will cause elf-objdump to crash in both 1.30 and 1.32B (so apparently it's not just 1.32B that is affected)
     
    a workaround will be to do as compiler manual suggests, add -mconst-in-code and
    volatile const __attribute__((address(0x200))) uint16_t reserved_space[256] = {0,};

    (because declaring the const without initializing it will always put the const in RAM)
    #5
    Jump to:
    © 2017 APG vNext Commercial Version 4.5