Starting gdbserver failed (VS2017 --> yocto) - linux

I am using VS2017 to compile and debug my cross platform C application on linux. With my Raspberry Pi it is working perfectly, but now I tryed it to debug it on a yocto system. Compilation works, but if I want to debug I am getting following messge: Starting gdbserver failed, this is unexpected and indicative of an incompatible or broken shell. Example command used on the shell: "echo 1; gdbserver; echo 2". We expected "1".
Visual Studio Message Box
On my remote machine gdbserver 7.10.1 is installed.

Related

Build and Run on Ubuntu VM

I just installed UTM on my M1 Macbook and am running ubuntu-20.04.4 as a Virtual Machine. I've been trying to build and run a code given for an assignment, as requested by the course professor.
An issue rose when I got 'make: g++: Command not found'. I therefore installed Developer tools through the command 'apt-get install build-essential'.
This is where I need help. The tools were installed, but running the 'make' command gave a different error 'g++: error: unrecognized command line error: -m64'.
Note: All the necessary files to build and run the code are provided (e.g: Makefile and Cpp file). I really just have to build and run to see the program output.

Compiling WebRTC Linux ARM on Windows Host

I spent 2 days trying to compile WebRTC for Raspbery PI.
I'm on Windows host and there is absolutely zero info in internet how to do this.
Linux WebRTC requires to run sysroot installation script. It just fails on windows due to some tar wrong options.
Somehow I managed to manually run tar though it gave me several hundreds errors regarding some symbolic links creation.
Next error is about some ptoto_library:
ERROR at //build/toolchain/win/BUILD.gn:15:1: Assertion failed.
assert(is_win)
^-----
See //third_party/protobuf/proto_library.gni:413:14: which caused the file to be included.
deps = [ _protoc_label ]
If I disable proto library it fails on compilation because of clang++ is not found.
Is there way to compile WebRTC for Linux from Windows host?
Strange that there is no any info about such possibility at all.

React Native app stuck on blank white screen with iOS simulator

I built my application with the Facebook login feature for iOS last week.
I don't know why but when I opened my app today I get this strange error.
** BUILD FAILED **
The following build commands failed:
CompileC /Users/alan2305/dougo/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/jschelpers.build/Objects-normal/x86_64/JSCWrapper.o /Users/alan2305/dougo/node_modules/react-native/ReactCommon/jschelpers/JSCWrapper.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
CompileC /Users/alan2305/dougo/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/jschelpers.build/Objects-normal/x86_64/Value.o /Users/alan2305/dougo/node_modules/react-native/ReactCommon/jschelpers/Value.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
CompileC /Users/alan2305/dougo/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/jschelpers.build/Objects-normal/x86_64/JSCHelpers.o /Users/alan2305/dougo/node_modules/react-native/ReactCommon/jschelpers/JSCHelpers.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
CompileC /Users/alan2305/dougo/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/jschelpers.build/Objects-normal/x86_64/Unicode.o /Users/alan2305/dougo/node_modules/react-native/ReactCommon/jschelpers/Unicode.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
(4 failures)
Installing build/Build/Products/Debug-iphonesimulator/dougo.app
An error was encountered processing the command (domain=IXUserPresentableErrorDomain, code=1):
This app could not be installed at this time.
Underlying error (domain=MIInstallerErrorDomain, code=4):
Failed to chmod /Users/alan2305/Library/Developer/CoreSimulator/Devices/27A18B40-AF2B-4FDF-A98C-796B1E53CC7B/data/Library/Caches/com.apple.containermanagerd/Bundle/Application/535974D3-D4A0-4EB1-AEE1-F7CBC7107F9B/dougo.app/dougo : No such file or directory
Launching org.reactjs.native.example.dougo
org.reactjs.native.example.dougo: 54919
Not able to find the solution to fix this please help.
here is my terminal error image
here is my XCode error image

Iceweasel crashes after loading in linux on android

I installed Kali Linux via Linux Deploy on my rooted G2x running CM 7 and everything is fine, however I installed Iceweasel and now it begins loading a webpage then crashes, the term output is
$ iceweasel
Xlib: extension "RANDR" missing on display ":0.0".
(iceweasel:5847): Gdk-WARNING **: shmget failed: error 38 (Function not implemented)
Segmentation fault
$
any ideas?

Remote debugging Beaglebone from a 64 bit machine

I am running Xubuntu on a 64 bit machine. When trying to debug a Beaglebone using gdb (via Eclipse) I get the following error message:
"Remote 'g' packet reply is too long"
See here for more details:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509479
At the host I am using gdb-multiarch.
When start it, it announces:
"This GDB was configured as "x86_64-linux-gnu"."
Can you please tell me how to configure GDB to work with a 32 bit target? Any other thoughts?
Thank you.
As far as I know the BeagleBone uses an ARM processor.
You'll have to get the ARM version (more precise: version for debugging ARM processors) of GDB to debug - you cannot do this with the x86 version.
For Windows the ARM version is available in the "WinARM" packet.
Maybe for Linux such a packet does not exist and you'll have to re-compile GDB.
Add "set architecture arm" to the .gdbinit file referenced in Eclipse under Debug Configurations -- Debugger -- GDB command file. Make sure the .gdbinit file can be found at run-time by making sure GDB command file contains full path to file.
I encountered a similar issue trying to set up cross compilation through Eclipse with a Ubuntu 12.04 Host VM running on a Mac connecting to a Beaglebone Black target. When trying to debug my project, I would get the same "Remote 'g' packet reply is too long" error. What solved this issue for me was to go into the Debug Configuration for your project, select the Debugger tab, and replace gdb to gdb-multiarch the GDB debugger field.

Resources