https://en.wikipedia.org/wiki/INT_(x86_instruction) (scroll down to INT3)

https://stackoverflow.com/a/61946177

The TL;DR is that it's used by debuggers to set a breakpoint in code.

For example, if you're familiar with gdb, one of the simplest ways to make code stop executing at a particular point in the code is to add a breakpoint there.

Gdb replaces the instruction at the breakpoint with 0xCC, which happens to be the opcode for INT 3

generate interrupt 3. When the CPU encounters the instruction, it generates interrupt 3, following which the kernel's interrupt handler sends a signal (SIGTRAP) to the debugger. Thus, the debugger will know it's meant to start a debugging loop there.

My daughter told me the other day, "I bet I could figure out a Commodore 64 if I had one."

Good luck figuring out LOAD "*",8,1 by yourself, kid.

Someone told me every processor used 0xEA

Not sure if this is a riff on the joke or not.

Back in the day I dabbled in 6510 code, and up until today hadn't even bothered to look at a chart of opcodes for any of its contemporaries. Today I learned that Z80 uses $00 for NOP.

Loth as I am to admit it, that actually makes sense. Maybe more sense than 65xx which acts more like a divide-by-zero has happened.

The rest of the opcode table was full of alien looking mnemonics though, and no undocumented single byte opcodes? Freaky, man.

But the point is that not even Z80 used $EA. If the someone was real they probably meant every 65xx processor.

https://www.explainxkcd.com/wiki/index.php/2501:_Average_Familiarity

The people in the picture are so used to working with assembly language, that even though they know the average person doesn’t know much about assembly, they assume the average person knows a little, which is already way more than the average person actually knows.

what's it called when you try to be aware of this and inadvertently say stuff that comes off as condescending, umm, asking for a friend

My friend really needs to learn about this. He works for Intel and does some really involved stuff, I on the other hand am a moronic jackass factory worker.

No friend, I haven't the slightest idea what you're trying to tell me you did if you keep using technical terms.

I think it is 0xCC, or in long form 0xCD03

I didn't even know they released int2

Just looked this up and subscribed to the channel.

I feel like I skipped right over this comment.

0x90^0x90^0x90^0x90^0x90^0x90^0x90^0x90^0x90^0x90^

That's the original

"So this here is a rock"
"Uhh, in english please?"

Things said by Github copilot.