If one day when using execve you encounter the “no such file or directory” problem, and that the file you tried to launch is really existing and with the good rights, then the problem is coming from the shebang not pointing to a valid interpreter.
In example: #!/bin/ksh and ksh is not installed
#reminder #execve
Month: June 2020
GDB, threads, sockets and SO_RCVTIMEO SO_SNDTIMEO options
Reminder:
A threaded program ran inside gdb and using blocking sockets will stop on a sigcatch : EINTR
Related stackoverflow link:
https://stackoverflow.com/questions/51666259/why-recv-returns-1-and-errno-eintr-when-set-so-rcvtimeo
New to GDB or in need of good ressources about it ?
Here you go:
https://www.st.com/resource/en/user_manual/usermanual_debugging_with_gdb-user-manual–debugging-with-gdb-for-stm32cubeide-stmicroelectronics.pdf
That manual I stumbled upon while searching for some informations on how to configure gdb is THE thing.
From starting to crashing, each possible good analysis is covered in that manual.
Good reading !
#debugger #code #gdb