3 Handmade Linux x86 executables: Loops and conditionals

This video series:

The Intel manual:

[amikomalania]

Hope you continue thi video series! good job

[codecraftercc]

i hope u know how cool that is lmao
i searched about two years ago how to do that and found nothing so i didnt do anything in that direction, but now i am able to do some asm testing, thx!

[broepi]

This is awesome! Are you planning to cover the import of shared libraries in your ELF?

[Brickostan]

Really interesting videos you've made (at least for me as nerd).
I'm not going to try to write programs this way myself - but before watching these videos I didn't know anything about ELF. Now I know some.
And a little more x86 machine code (not that I'm ever gonna use it in real life)

[HumbleHuman-kg]

Nice abilities !!!
let's hope he will continue further on that rhythm.

[oleh]

At 2:31 you can use CTRL+v to enter visual block mode, select all wrong byte count and overwrite them with:
c space space ESC

😉

[nickpelov]

I noticed something interesting. The program never reaches the exit syscall and doesn't have and error handing for write, and yet when the pipe (to head) was closed. A after quick googling I saw that SIGPIPE is sent to the process when writes to a "broken" pipe. I know that singlals have handlers and some signals have default handlers, but I thgought that the default handler is in the executable, generated by the compiler. So if the default handler is not in the executable itself does it execute as a part of the process or it's a part of the kernel containing the code "kill <the pid>" ... wait kill also sends a signal. So how does a code (default handler) executes as a part of this program?