I have built the linux kernel 3.14 with debug info. When I tried to boot it gives following error and after that booting freezes
Can somebody tell me how to fix this ?
Linux Version : Slitaz in Qemu
Related
I'm trying to debug my st device(STM32F401CCU6) remotely. I'm using raspberry pi 3 for debugger. I had install openocd on RPI. I set everything up in STM32CUBEIDE 1.8.0.
When I debug my code appears this message box. I search a while. I did configure "stm32f4xx.cfg" file for device ID.
RPI3 ready to debug
STM32CUBEIDE 1.8.0
I did solve with downgrade from STM32CUBEIDE v1.8.0 to v1.6.0. I can flash program and debug. But there is one more issue. I want to use live expressions when debugging. But it doesn't work like this.
When I try to run Rstudio Desktop (1.4) on my virtual machine (Ubuntu 16.4), Rstudio crashes and gives the error:
ERROR:gl_surface_glx_gt.cpp(141) GLX 1.3 or later is required.
I tried to follow the instructions on this page: https://wiki.x2go.org/doku.php/wiki:development:glx-xlib-workaround, but can not get past the meson -D configuration in the Ubuntu terminal. At this point I get the error message: 'ERROR: Problem encountered: gallium-xlib conflicts with any dri driver'
I googled and tried everything that I could possibly find (similar questions as https://community.rstudio.com/t/x2go-and-rstudio/29704/2), but no success yet.
Obviously the upgrade to a higher GLX version is the cause, but I can not upgrade it.
Is anyone familiar with the error and what is actually causing it?
Any help would be greatly appreciated!
I am using R version 3.4.4
It's too hard to debug a MPI program using GDB. I've tried to buy parallel debugger but failed .
I found Eclipse has a parallel debug plugin(Eclipse PTP or Eclipse science),but I can't use it!
I'm using:
ubuntu 18.04
openJDK 11.0.2
eclipse-parallel 2019-03-R
When I setting run>run configurations:
1.Target System Configuration:Generic OpenMPI Interactive
2.Connection Type:Local
error occur
Launch Error:
Provider com.sun.xml.internal.bind.v2.ContextFactory not found
Reason:com.sun.xml.internal.bind.v2.ContextFactory cannot be found
by org.eclipse.ptp.rm.jaxb.core_1.2.0.201811201954
I've tried to download different version of eclipse:
eclipse before 2017:I can't open it ,there is something wrong with openJDK 11
eclipse-parallel-photon-R: When i click "local" in configuration,nothing happened...
I also had same problem. If you still suffer / somebody has the same problem, it seems it is fixed in the latest version 201906. You can download using installer from:
https://www.eclipse.org/downloads/download.php?file=/oomph/epp/2019-06/M2/eclipse-inst-linux64.tar.gz
I'm using ubuntu 18.04 and trying to boot kernel 2.6.34.7 compiled from source. I tried to boot from ubuntu but it says "kernel too old", then I came up with the idea of using qemu, but I got the same problem... The version of my QEMU emulator is 2.11.1, the error code is:
...
FATAL: kernel too old
[ 5.299747] Kernel panic - not syncing: Attempted to kill init!
[ 5.300415] Pid: 1, comm: init Not tainted 2.6.34.7 #1
...
This is not a problem with QEMU. The "FATAL: kernel too old" message comes from your guest's userspace, specifically its glibc. Your guest's userspace binaries were built to require a newer kernel than the one you're trying to boot, so the two are not compatible. You need to either use a set of userspace binaries (ie a disk image) which was built to work with that old kernel, or you need to use a newer kernel that will work with the binaries you're using.
I was, until recently able to boot qemu-system-ppc (v1.7.0) using a customized cross compiled Linux kernel and BusyBox. I even posted it here: qemu kernel debugging with KGDB
However I am unable to do so now with v2.0.2. The command I use to invoke qemu is the very same I used previously
qemu-system-ppc -M mpc8544ds -m 512 -kernel zImage -s -nographic -initrd busyboxfs.img -append "root=/dev/ram rdinit=/bin/sh kgdboc=ttyS0,115200 kgdbwait
can anyone help me see the console log so I can understand if it is indeed booting and if not what is the problem. I've tried without the kgdb arguments to the kernel but still all I see is blank.
You might want to have a look at Buildroot (http://www.buildroot.org) : we have three PowerPC defconfigs that boot fine under recent versions of Qemu, including 2.0.2 and 2.1.2.
See especially the qemu_ppc_g3beige_defconfig, which boots fine under Qemu 2.1.2, the qemu_ppc_mpc8544ds_defconfig, which boots fine under Qemu 2.0.2, and qemu_ppc_virtex_ml507_defconfig, which boots fine under Qemu 2.1.2.