qemu: uncaught target signal 11 (Segmentation fault) - embedded-linux

Inside scratch box i am performing git clone, getting following error:
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Error:
/pi$ sb2 -t rfs-raspbian -eR git clone git://github.com/danwinship/glib.git
Cloning into 'glib'...
remote: Counting objects: 72484, done.
remote: Compressing objects: 100% (11555/11555), done.
remote: Total 72484 (delta 61357), reused 71916 (delta 60808)
Receiving objects: 100% (72484/72484), 28.86 MiB | 59 KiB/s, done.
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
error: index-pack died of signal 11
fatal: index-pack failed
QEmu version installed :
qemu-arm -version
qemu-arm version 1.3.90, Copyright (c) 2003-2008 Fabrice Bellard
qemu-system-arm -version
QEMU emulator version 1.3.90, Copyright (c) 2003-2008 Fabrice Bellard
Any suggestion how to resolve it ?

I've obtained the same error while running git in qemu-static-aarch64 chroot. I've resolved this problem by compiling git without threads use.

Related

hwloc/linux warning and PETSc Segmentation Violation error

I am trying to run a program using mpirun command (as shown below).
mpirun -np 4 python test.py
But I am getting following warning first:
hwloc/linux: Ignoring PCI device with non-16bit domain.
Pass --enable-32bits-pci-domain to configure to support such devices
(warning: it would break the library ABI, don't enable unless really needed).
hwloc/linux: Ignoring PCI device with non-16bit domain.
Pass --enable-32bits-pci-domain to configure to support such devices
(warning: it would break the library ABI, don't enable unless really needed).
hwloc/linux: Ignoring PCI device with non-16bit domain.
Pass --enable-32bits-pci-domain to configure to support such devices
(warning: it would break the library ABI, don't enable unless really needed).
hwloc/linux: Ignoring PCI device with non-16bit domain.
Pass --enable-32bits-pci-domain to configure to support such devices
(warning: it would break the library ABI, don't enable unless really needed).
Program also depends on PETSc, after the above warning, it shows following error:
[1]PETSC ERROR: ------------------------------------------------------------------------
[1]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[1]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[1]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind
[1]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors
[1]PETSC ERROR: likely location of problem given in stack below
[1]PETSC ERROR: --------------------- Stack Frames ------------------------------------
[1]PETSC ERROR: Note: The EXACT line numbers in the stack are not available,
[1]PETSC ERROR: INSTEAD the line number of the start of the function
[1]PETSC ERROR: is given.
[1]PETSC ERROR: --------------------- Error Message --------------------------------------------------------------
[1]PETSC ERROR: Signal received
[1]PETSC ERROR: See https://petsc.org/release/faq/ for trouble shooting.
[1]PETSC ERROR: Petsc Release Version 3.15.5, Sep 29, 2021
[1]PETSC ERROR: Unknown Name on a real-debug named skynet by pavan Sat Jun 18 10:30:04 2022
[1]PETSC ERROR: Configure options --PETSC_ARCH=real-debug --with-scalar-type=real --with-debugging=1 --with-mpi-dir=/home/pavan/packages/openmpi-4.0.7/opt-gfortran --download-metis=yes --download-parmetis=yes --download-superlu_dist=yes --with-shared-libraries=yes --with-fortran-bindings=1 --with-cxx-dialect=C++11
[1]PETSC ERROR: #1 User provided function() at unknown file:0
[1]PETSC ERROR: Checking the memory for corruption.
[2]PETSC ERROR: ------------------------------------------------------------------------
[2]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[2]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[2]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind
[2]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors
[2]PETSC ERROR: likely location of problem given in stack below
[2]PETSC ERROR: --------------------- Stack Frames ------------------------------------
[2]PETSC ERROR: Note: The EXACT line numbers in the stack are not available,
[2]PETSC ERROR: INSTEAD the line number of the start of the function
[2]PETSC ERROR: is given.
[2]PETSC ERROR: --------------------- Error Message --------------------------------------------------------------
[2]PETSC ERROR: Signal received
[2]PETSC ERROR: See https://petsc.org/release/faq/ for trouble shooting.
[2]PETSC ERROR: Petsc Release Version 3.15.5, Sep 29, 2021
[2]PETSC ERROR: Unknown Name on a real-debug named skynet by pavan Sat Jun 18 10:30:04 2022
[2]PETSC ERROR: Configure options --PETSC_ARCH=real-debug --with-scalar-type=real --with-debugging=1 --with-mpi-dir=/home/pavan/packages/openmpi-4.0.7/opt-gfortran --download-metis=yes --download-parmetis=yes --download-superlu_dist=yes --with-shared-libraries=yes --with-fortran-bindings=1 --with-cxx-dialect=C++11
[2]PETSC ERROR: #1 User provided function() at unknown file:0
[2]PETSC ERROR: Checking the memory for corruption.
[3]PETSC ERROR: ------------------------------------------------------------------------
[3]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[3]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[3]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind
[3]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors
[3]PETSC ERROR: likely location of problem given in stack below
[3]PETSC ERROR: --------------------- Stack Frames ------------------------------------
[3]PETSC ERROR: Note: The EXACT line numbers in the stack are not available,
[3]PETSC ERROR: INSTEAD the line number of the start of the function
[3]PETSC ERROR: is given.
[3]PETSC ERROR: --------------------- Error Message --------------------------------------------------------------
[3]PETSC ERROR: Signal received
[3]PETSC ERROR: See https://petsc.org/release/faq/ for trouble shooting.
[3]PETSC ERROR: Petsc Release Version 3.15.5, Sep 29, 2021
[3]PETSC ERROR: Unknown Name on a real-debug named skynet by pavan Sat Jun 18 10:30:04 2022
[3]PETSC ERROR: Configure options --PETSC_ARCH=real-debug --with-scalar-type=real --with-debugging=1 --with-mpi-dir=/home/pavan/packages/openmpi-4.0.7/opt-gfortran --download-metis=yes --download-parmetis=yes --download-superlu_dist=yes --with-shared-libraries=yes --with-fortran-bindings=1 --with-cxx-dialect=C++11
[3]PETSC ERROR: #1 User provided function() at unknown file:0
[3]PETSC ERROR: Checking the memory for corruption.
[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[0]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind
[0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors
[0]PETSC ERROR: likely location of problem given in stack below
[0]PETSC ERROR: --------------------- Stack Frames ------------------------------------
[0]PETSC ERROR: Note: The EXACT line numbers in the stack are not available,
[0]PETSC ERROR: INSTEAD the line number of the start of the function
[0]PETSC ERROR: is given.
[0]PETSC ERROR: --------------------- Error Message --------------------------------------------------------------
[0]PETSC ERROR: Signal received
[0]PETSC ERROR: See https://petsc.org/release/faq/ for trouble shooting.
[0]PETSC ERROR: Petsc Release Version 3.15.5, Sep 29, 2021
[0]PETSC ERROR: Unknown Name on a real-debug named skynet by pavan Sat Jun 18 10:30:04 2022
[0]PETSC ERROR: Configure options --PETSC_ARCH=real-debug --with-scalar-type=real --with-debugging=1 --with-mpi-dir=/home/pavan/packages/openmpi-4.0.7/opt-gfortran --download-metis=yes --download-parmetis=yes --download-superlu_dist=yes --with-shared-libraries=yes --with-fortran-bindings=1 --with-cxx-dialect=C++11
[0]PETSC ERROR: #1 User provided function() at unknown file:0
[0]PETSC ERROR: Checking the memory for corruption.
I am new to mpi, so I don't really know what is going here. Any help will be much appreciated. Following are the additional details which might be useful:
System: Ubuntu 22.04
OpenMPI - 4.0.7
PETSc - 3.15.5. Configured PETSc as follows:
./configure --PETSC_ARCH=$PETSC_ARCH --with-scalar-type=real --with-debugging=1 --with-mpi-dir=$MPI_INSTALL_DIR \
--download-metis=yes --download-parmetis=yes --download-superlu_dist=yes \
--with-shared-libraries=yes --with-fortran-bindings=1 --with-cxx-dialect=C++11
Python - 3.9.12
gfortran - 9.4.0
gcc - 9.4.0

VAGRANT ERROR Command: ["hostonlyif", "create"]

I am using MacOSbigsur, Macbook Pro, M1 Chip,
I installed Virtual box the latest version 6.1.26r145957, use this command for confirmation (VBoxManage --version).
I installed Vagrant 2.2.18, use this command for confirmation (Vagrant --version).
I clone the repo from https://box.scotch.io/, and then type on terminal "vagrant up"
Following an error occurs, I try many solutions available on the internet but not fixed. I uninstall both software and re-install did not work for me, permission is ok from system preference.
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["hostonlyif", "create"]
Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open
/dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component
HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 95 of file VBoxManageHostonly.cpp
Possible Solution: sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart
when I run this command its shows the following errors
Loading VBoxDrv.kext
Incompatible architecture: Binary is for x86_64, but needed arch arm64e
Error: Failed to load org.virtualbox.kext.VBoxDrv
Loading VBoxUSB.kext
Incompatible architecture: Binary is for x86_64, but needed arch arm64e
Error: Failed to load org.virtualbox.kext.VBoxUSB
Loading VBoxNetFlt.kext
Incompatible architecture: Binary is for x86_64, but needed arch arm64e
Error: Failed to load org.virtualbox.kext.VBoxNetFlt
Loading VBoxNetAdp.kext
Incompatible architecture: Binary is for x86_64, but needed arch arm64e
Error: Failed to load org.virtualbox.kext.VBoxNetAdp
Executing: /usr/bin/kmutil unload -b org.virtualbox.kext.VBoxNetAdp
Error occurred unloading extensions: Missing extension with identifier org.virtualbox.kext.VBoxNetAdp : Incompatible
architecture: Binary is for x86_64, but needed arch arm64e
Executing: /usr/bin/kmutil unload -b org.virtualbox.kext.VBoxNetFlt
Error occurred unloading extensions: Missing extension with identifier org.virtualbox.kext.VBoxNetFlt : Incompatible
architecture: Binary is for x86_64, but needed arch arm64e
Executing: /usr/bin/kmutil unload -b org.virtualbox.kext.VBoxUSB
Error occurred unloading extensions: Missing extension with identifier org.virtualbox.kext.VBoxUSB : Incompatible architecture: Binary is for x86_64, but needed arch arm64e
Executing: /usr/bin/kmutil unload -b org.virtualbox.kext.VBoxDrv
Error occurred unloading extensions: Missing extension with identifier org.virtualbox.kext.VBoxDrv : Incompatible architecture: Binary is for x86_64, but needed arch arm64e
Fatal error: VirtualBox
I had a similar error.
Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 95 of file VBoxManageHostonly.cpp
Was able resolve simply by going to security settings and adding allow from Oracle.
For me this occurred after updating Mac OS, Oracle VB and Vagrant. Currently on Mac Os Monterey 12.3.1

An error when install cutorch in Torch7 of centos7

I want to install the cutorch and get an error and I don't know how to solve it:
(tf0.12.1) [root#sd-bigdata-gpu-02 deepmask]# luarocks install cutorch
Installing https://raw.githubusercontent.com/torch/rocks/master/cutorch-scm-1.rockspec...
Using https://raw.githubusercontent.com/torch/rocks/master/cutorch-scm-1.rockspec... switching to 'build' mode
Cloning into 'cutorch'...
remote: Counting objects: 227, done.
remote: Compressing objects: 100% (180/180), done.
remote: Total 227 (delta 64), reused 91 (delta 45), pack-reused 0
Receiving objects: 100% (227/227), 234.16 KiB | 0 bytes/s, done.
Resolving deltas: 100% (64/64), done.
Warning: unmatched variable LUALIB
jopts=$(getconf _NPROCESSORS_CONF)
……
[ 81%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/generated/./THC_generated_THCTensorMaskedDouble.cu.o
Scanning dependencies of target THC
[ 82%] [ 84%] [ 85%] [ 86%] [ 87%] [ 88%] [ 89%] [ 90%] [ 92%] Building CXX object lib/THC/CMakeFiles/THC.dir/THCCachingAllocator.cpp.o
Building CXX object lib/THC/CMakeFiles/THC.dir/THCCachingHostAllocator.cpp.o
Building C object lib/THC/CMakeFiles/THC.dir/THCGeneral.c.o
Building C object lib/THC/CMakeFiles/THC.dir/THCStorageCopy.c.o
Building C object lib/THC/CMakeFiles/THC.dir/THCTensor.c.o
Building C object lib/THC/CMakeFiles/THC.dir/THCTensorCopy.c.o
Building CXX object lib/THC/CMakeFiles/THC.dir/THCStream.cpp.o
Building CXX object lib/THC/CMakeFiles/THC.dir/THCTensorRandom.cpp.o
Building C object lib/THC/CMakeFiles/THC.dir/THCThreadLocal.c.o
In file included from generic/THCTensor.c:1:0,
from /tmp/luarocks_cutorch-scm-1-4055/cutorch/lib/THC/THCGenerateAllTypes.h:17,
from /tmp/luarocks_cutorch-scm-1-4055/cutorch/lib/THC/THCTensor.c:7:
/tmp/luarocks_cutorch-scm-1-4055/cutorch/lib/THC/generic/THCTensor.c: In function ‘THCudaByteTensor_newExpand’:
/tmp/luarocks_cutorch-scm-1-4055/cutorch/lib/THC/generic/THCTensor.c:304:3: error: implicit declaration of function ‘THLongStorage_calculateExpandGeometry’ [-Werror=implicit-function-declaration]
THLongStorage_calculateExpandGeometry(tensor->size,
^
cc1: some warnings being treated as errors
make[2]: *** [lib/THC/CMakeFiles/THC.dir/THCTensor.c.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [lib/THC/CMakeFiles/THC.dir/all] Error 2
make: *** [all] Error 2
Error: Build error: Failed building.
(tf0.12.1) [root#sd-bigdata-gpu-02 deepmask]# lspci | grep -i 'vga\|3d\|2d'
02:00.0 3D controller: NVIDIA Corporation GM200GL [Tesla M40] (rev a1)
03:00.0 3D controller: NVIDIA Corporation GM200GL [Tesla M40] (rev a1)
06:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30)
83:00.0 3D controller: NVIDIA Corporation GM200GL [Tesla M40] (rev a1)
84:00.0 3D controller: NVIDIA Corporation GM200GL [Tesla M40] (rev a1)
I have install the cude 8.0 and cudnn . And I could also install other packages like nnx, optim, inn sucessfully.
I also encountered this. The cause is due to a new method in the torch lib, see: https://github.com/torch/torch7/blob/master/lib/TH/THStorage.c#L69
Update Torch by running luarocks install torch before luarocks install cutorch and you should be good to go.

xcodebuild exited with code 65 :EddyVerbruggen/SocialSharing-PhoneGap-Plugin

I am trying to add socialSharing to my IBM mobileFirst hybrid app.. Added the 'socialsharing.h','socialsharing.m' file but I get an error doing the Xcodebuild (cli)
The error is:
The following build commands failed:
CompileC /Users/Pre/Library/Developer/Xcode/DerivedData/RandstadJobs-awbivrwbculwbcbkdgifcfkukrfk/Build/Intermediates/ArchiveIntermediates/RandstadMobileRandstadRecruiterIphone/IntermediateBuildFilesPath/RandstadJobs.build/Distribution-iphoneos/RandstadMobileRandstadRecruiterIphone.build/Objects-normal/armv7/SocialSharing.o Classes/SocialSharing.m normal armv7 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
xcodebuild exited with code: 65
[17:23:39] 'build-iphone-no-deps' errored after 14 s
[17:23:39] RunCommandError: xcodebuild did not complete [code, signal]: 65,
at _doneHandler (/Users/Pre/Documents/Development/mymobile/dev/Recruiter/build/node_modules/build-common/tasks.js:319:19)
at ChildProcess. (/Users/Prem/Documents/Development/mymobile/dev/Recruiter/build/node_modules/build-common/tasks.js:300:12)
at ChildProcess.emit (events.js:110:17)
at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
[17:23:39] 'build-apps' errored after 42 s
[17:23:39] Error in plugin 'run-sequence(build-iphone-no-deps)'
Message:
build-iphone-no-deps callback
I am using Xcode v7.3 and IBM mobile first 7.1
Can you please provide some hints on how to fix this issue
Thanks
You can MobileFirst-related instructions here: How we can implement add to any(Social networking) in MobileFirst
Xcode-wise make sure you did not forget to add the following frameworks:
MessageUI.framework
Social.framework
Try cleaning up your derived data.

make[1]: ***No rule to make target 'zynq_xcomm_adv7511_deconfig'

I've looked through a few of the posts relating to the error and can't see one which covers this specific circumstance. I'm trying to compile a kernel image as defined in these steps from a tutorial;
git clone https://github.com/analogdevicesinc/linux.git
Cloning into 'linux'...
remote: Counting objects: 2550298, done.
remote: Compressing objects: 100% (466978/466978), done.
remote: Total 2550298 (delta 2118600), reused 2483072 (delta 2058083)
Receiving objects: 100% (2550298/2550298), 727.70 MiB | 353 KiB/s, done.
Resolving deltas: 100% (2118600/2118600), done.
Checking out files: 100% (38170/38170), done.
> cd linux
> git checkout xcomm_zynq
> # For AD-FMCOMMS2-EBZ use
> # git checkout xcomm_zynq
> export ARCH=arm
> export CROSS_COMPILE=/path/to/your/arm/cross-compiler
> # e.g. export CROSS_COMPILE=/opt/CodeSourcery/Sourcery_G++_Lite/bin/arm-xilinxa9-linux-gnueabi-
> make zynq_xcomm_adv7511_defconfig
#
# configuration written to .config
#
> make uImage LOADADDR=0x00008000
...
OBJCOPY arch/arm/boot/uImage
Kernel: arch/arm/boot/uImage is ready
I've followed all the steps up until I do the first make and get the error;
make[1]: ***No rule to make target 'zynq_xcomm_adv7511_deconfig'
I know very little about make and generally have used it blindly in the past. What does this error point towards? The Makefile should be fine as it's issued from Analog. The only difference is I'm using a different cross compiler - that being arm-linux-gnueabihf-gcc instead. Would this cause a problem?
There is a typo somewhere. It needs to be called zynq_xcomm_adv7511_defconfig

Resources