Forums - make tree V=android_Debug segfaults

1 post / 0 new
make tree V=android_Debug segfaults
mbuch
Join Date: 28 Oct 19
Posts: 3
Posted: Sat, 2020-04-04 18:30

I am building the calculator example in the Hexagon SDK 3.5.1. I ran the setup and then:

make tree V=android_Debug VERBOSE=1

I get following error:

/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/build/make.d.ext/android/defines_android_Debug.min:32:
 "Using default tools location: ANDROID_TOOLS_DIR=/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/tool
s/android-ndk-r19c/toolchains/llvm/prebuilt/linux-x86_64"
/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/build/make.d.ext/android/defines_android_Debug.min:41:
 "Using default platform location: ANDROID_PLATFORM_DIR=/home/gardei/Qualcomm/Hexagon_SDK/3.5.
1/tools/android-ndk-r19c/platforms/android-26/arch-arm"
************  LIB=libadsprpc ************
making /home/gardei/Qualcomm/Hexagon_SDK/3.5.1/tools/qaic
make[1]: Entering directory '/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/tools/qaic'
Qaic's Another IDL Compiler: version 1.0.40.1239026
Copyright (c) 2012 QUALCOMM Inc. All rights reserved.
make[1]: Leaving directory '/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/tools/qaic'
making /home/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/common/atomic
make[1]: Entering directory '/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/common/atomic'
making /home/gardei/Qualcomm/Hexagon_SDK/3.5.1/tools/qaic
make[2]: Entering directory '/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/tools/qaic'
make[2]: 'bin/qaic' is up to date.
make[2]: Leaving directory '/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/tools/qaic'
making .
make[2]: Entering directory '/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/common/atomic'
/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/tools/android-ndk-r19c/toolchains/llvm/prebuilt/linux-
x86_64/bin/armv7a-linux-androideabi26-clang -target arm-linux-androideabi26 -mthumb  -c -fpie
-fpic -fPIE -fPIC -Wall -Wno-missing-braces -march=armv7-a -Werror -g -isystem /home/gardei/Qu
alcomm/Hexagon_SDK/3.5.1/tools/android-ndk-r19c/platforms/android-26/arch-arm/usr/include -D_A
NDROID_ -DANDROID -std=gnu99           -D__FILENAME__=\"atomic.c\" -D_DEBUG  -I= -I/home/garde
i/Qualcomm/Hexagon_SDK/3.5.1/incs -I/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/incs/stddef -I/hom
e/gardei/Qualcomm/Hexagon_SDK/3.5.1/incs/qnx -I/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/co
mmon/remote/ship/android_Debug -I/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/common/qnx/ship/
android_Debug -I/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/common/rtld/ship/android_Debug -I
/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/common/apps_mem_heap/ship/android_Debug -Iinc -Ia
ndroid_Debug  -oandroid_Debug/atomic.o src/atomic.c
/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/tools/android-ndk-r19c/toolchains/llvm/prebuilt/linux-
x86_64/bin/armv7a-linux-androideabi26-clang -target arm-linux-androideabi26 -mthumb  -c -fpie
-fpic -fPIE -fPIC -Wall -Wno-missing-braces -march=armv7-a -Werror -g -isystem /home/gardei/Qu
alcomm/Hexagon_SDK/3.5.1/tools/android-ndk-r19c/platforms/android-26/arch-arm/usr/include -D_A
NDROID_ -DANDROID -std=gnu99           -D__FILENAME__=\"cae.c\" -D_DEBUG  -I= -I/home/gardei/Q
ualcomm/Hexagon_SDK/3.5.1/incs -I/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/incs/stddef -I/home/g
ardei/Qualcomm/Hexagon_SDK/3.5.1/incs/qnx -I/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/commo
n/remote/ship/android_Debug -I/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/common/qnx/ship/and
roid_Debug -I/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/common/rtld/ship/android_Debug -I/ho
me/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/common/apps_mem_heap/ship/android_Debug -Iinc -Iandr
oid_Debug  -oandroid_Debug/cae.o src/cae.c
cat: android_Debug/atomic_a_archiver.txt: No such file or directory
/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/tools/android-ndk-r19c/toolchains/llvm/prebuilt/linux-
x86_64/bin/llvm-ar @android_Debug/atomic_a_archiver.txt
/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/tools/android-ndk-r19c/toolchains/llvm/prebuilt/linux-
x86_64/bin/armv7a-linux-androideabi26-clang -target arm-linux-androideabi26 -mthumb  -c -fpie
-fpic -fPIE -fPIC -Wall -Wno-missing-braces -march=armv7-a -Werror -g -isystem /home/gardei/Qu
alcomm/Hexagon_SDK/3.5.1/tools/android-ndk-r19c/platforms/android-26/arch-arm/usr/include -D_A
NDROID_ -DANDROID -std=gnu99           -D__FILENAME__=\"atomic_q.c\" -D_DEBUG  -I= -I/home/gar
dei/Qualcomm/Hexagon_SDK/3.5.1/incs -I/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/incs/stddef -I/h
ome/gardei/Qualcomm/Hexagon_SDK/3.5.1/incs/qnx -I/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/
common/remote/ship/android_Debug -I/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/common/qnx/shi
p/android_Debug -I/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/common/rtld/ship/android_Debug
-I/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/common/apps_mem_heap/ship/android_Debug -Iinc -
Iandroid_Debug  -oandroid_Debug/atomic_q.o src/atomic_q.c
cat: android_Debug/atomic_q_link.txt: No such file or directory
/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/tools/android-ndk-r19c/toolchains/llvm/prebuilt/linux-
x86_64/bin/armv7a-linux-androideabi26-clang++ -target arm-linux-androideabi26 -mthumb @android
_Debug/atomic_q_link.txt
echo ok android_Debug/atomic_q
ok android_Debug/atomic_q
qemu-arm  android_Debug/atomic_q
qemu: uncaught target signal 11 (Segmentation fault) - core dumped

/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/build/make.d/rules.min:609: recipe for target 'android
_Debug/atomic_q.ok' failed
make[2]: *** [android_Debug/atomic_q.ok] Segmentation fault (core dumped)
make[2]: Leaving directory '/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/common/atomic'
/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/build/defines.min:62: recipe for target 'tree' failed
make[1]: *** [tree] Error 2
make[1]: Leaving directory '/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/libs/common/atomic'
/home/gardei/Qualcomm/Hexagon_SDK/3.5.1/build/defines.min:74: recipe for target 'ATOMIC' faile
d
make: *** [ATOMIC] Error 2
 

Looks like the call to qemu-arm is segfaulting. Has anyone encountered this before?

  • Up0
  • Down0

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.