may help you . The RLIMIT_CORE is used to place a limit on the amount of info that coredump is allowed to produce, before it is aborted. Once this limit is hit, no more info is logged and the message Aborting Core is logged to the console. From the man page of core :
Cross compiling for Linux on Windows (linker output file won't run as executable on linux and has undefined symbols)
this will help The "No such file or directory" error can be a bit confusing if the file is there and executable. You will also get that error on executing a file if the ELF interpreter (the program that performs the shared library linking) isn't found. That is what happens here. The relevant lines from readelf -l Test:
INTERP 0x0000000000000238 0x0000000000400238 0x0000000000400238
0x000000000000002e 0x000000000000002e R 1
[Requesting program interpreter: I:\Linux\libs\lib\x86_64-linux-gnu\ld-2.17.so]
around this issue I think the main problem is the different architecture. Your board is ARM while your Desktop is x86. Your application needs to be compiled on the board. Also you need to get the library files for arm.
Linux, how to execute an executable / non-executable file?
This might help you What is supposed to happen to an executable that deletes itself as part of its execution? Are the rules different for different OSes? Does it depend on the executable format (eg PE, Mach-O, etc) or on something else? , Are the rules different for different OSes?