Forums - hexagon-ar.exe crash

7 posts / 0 new
Last post
hexagon-ar.exe crash
mrelusive0
Join Date: 28 Jul 15
Posts: 5
Posted: Tue, 2016-05-10 15:08

The Windows hexagon-ar.exe from the 7.2.08 HEXAGON_Tools keeps crashing. Using the hexagon-ar.exe from an older version of the Hexagon_tools (say 5.0.14) works fine for older Hexagon architectures. However, it results in the following when trying to compile with V_ARCH=v60:

Unsupported machine architecure 0

BFD: BFD (Sourcery QuIC Lite 5.0-447) 2.20 20091016 internal error, aborting at /scratch/jwlemke/b4/quic-5_0-elf-1/obj/b

inutils-src-5.0-447-hexagon-i686-mingw32/bfd/elf32-hexagon.c line 885 in hexagon_elf_object_p

BFD: Please report this bug.

  • Up0
  • Down0
chenna
Join Date: 4 Feb 16
Posts: 54
Posted: Wed, 2016-05-11 05:46

5.0.14 hexagon-ar does not recognize v60 , can you make sure that you are using 7.2.08 hexagon-ar for v60, provide the crash details with 7.2.08 hexagon-ar

 

  • Up0
  • Down0
mrelusive0
Join Date: 28 Jul 15
Posts: 5
Posted: Wed, 2016-05-11 17:36

The only reason I tried the hexagon-ar.exe from 5.0.14 tools was to see if that one didn't crash.

I just switched to the 7.2.12 tools and the hexagon-ar.exe is still crashing.

'hexagon-ar.exe' (Win32): Loaded 'C:\Qualcomm\HEXAGON_Tools\7.2.12\Tools\bin\hexagon-ar.exe'. Cannot find or open the PDB file.
'hexagon-ar.exe' (Win32): Loaded 'C:\Windows\System32\ntdll.dll'. Cannot find or open the PDB file.
'hexagon-ar.exe' (Win32): Loaded 'C:\Windows\System32\kernel32.dll'. Cannot find or open the PDB file.
'hexagon-ar.exe' (Win32): Loaded 'C:\Windows\System32\KernelBase.dll'. Cannot find or open the PDB file.
'hexagon-ar.exe' (Win32): Loaded 'C:\Windows\System32\msvcr120.dll'. Cannot find or open the PDB file.
'hexagon-ar.exe' (Win32): Loaded 'C:\Windows\System32\advapi32.dll'. Cannot find or open the PDB file.
'hexagon-ar.exe' (Win32): Loaded 'C:\Windows\System32\msvcrt.dll'. Cannot find or open the PDB file.
'hexagon-ar.exe' (Win32): Loaded 'C:\Windows\System32\sechost.dll'. Cannot find or open the PDB file.
'hexagon-ar.exe' (Win32): Loaded 'C:\Windows\System32\rpcrt4.dll'. Cannot find or open the PDB file.
The thread 0x2d04 has exited with code 0 (0x0).
Unhandled exception at 0x00007FFD37D8CDA1 (msvcr120.dll) in hexagon-ar.exe: 0xC0000005: Access violation reading location 0x0000000044810750.
 
  msvcr120.dll!00007ffd37d8cda1() Unknown
  msvcr120.dll!00007ffd37d8660c() Unknown
  hexagon-ar.exe!00007ff706b52fb7() Unknown
  hexagon-ar.exe!00007ff706b52c91() Unknown
  hexagon-ar.exe!00007ff706b516dc() Unknown
  hexagon-ar.exe!00007ff706b7724b() Unknown
 
I can also provide one of the object files it crashes on if that helps.
 
Thanks!
 
  • Up0
  • Down0
chenna
Join Date: 4 Feb 16
Posts: 54
Posted: Thu, 2016-05-12 10:09

Are you running it on windows 8 ? Hexagon tools are not officially supported on windows 8/10

  • Up0
  • Down0
mrelusive0
Join Date: 28 Jul 15
Posts: 5
Posted: Thu, 2016-05-12 11:28

I'm using Windows 8.1.

I'd be a little surprised if hexagon-ar.exe needs anything that wouldn't work on Windows 8.1. The older hexagon-ar.exe works on Windows 8.1. It just doesn't support the new Hexagon versions.

  • Up0
  • Down0
bmaj7
Join Date: 28 Feb 18
Posts: 4
Posted: Wed, 2018-02-28 06:11

Has anyone found a solution to this? Please?! I am facing this issue running V.7.2.12 and I am living in the year 2018. No chance in switching back to Win7.

Pretty annoying. Lost half of the day due to this issue.

  • Up0
  • Down0
bmaj7
Join Date: 28 Feb 18
Posts: 4
Posted: Mon, 2018-03-05 02:33

In case someone is still facing issues with hexagon-ar.exe in recent Windows Versions, here is how to fix it:

1. Download the MinGW
2. Rename the hexagon-ar.exe to _hexagon-ar.exe in the hexagon tools/bin folder (or delete it)
3. Copy the C:\MinGW\bin\ar.exe utility to the hexagon Tools\bin\ and rename it to hexagon-ar.exe

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.