168
submitted 15 hours ago* (last edited 8 hours ago) by bi_tux@lemmy.world to c/programmerhumor@lemmy.ml

This happend to me right noww as I tried to write a gui task manager for the GNU/Linux OS

top 18 comments
sorted by: hot top controversial new old
[-] Hupf@feddit.org 5 points 5 hours ago

My first programming related memory is of the QBasic interpreter.

I had written some code I was quite happy with, but not saved it yet. As part of a subroutine for sound output, I quickly wrote a loop from 20 to 20000 to output a test signal over 1 second each with that frequency via the PC speaker and hit execute.

Realizing my mistake, It being MS-DOS and thus single-threaded, I couldn't Ctrl+C out of it without killing QBasic altogether and losing my code. I couldn't turn town the PC speaker.

I ended up closing various doors between the PC and me and waiting it out.

[-] deegeese@sopuli.xyz 20 points 13 hours ago

This is why VM snapshotting is so valuable.

My IDE is my real workstation, and it hosts a VM in which I can plop some code, run it, crash, revert and try again.

[-] deathmetal27@lemmy.world 30 points 15 hours ago

Try it again

Do you know the definition of insanity?

[-] bi_tux@lemmy.world 38 points 15 hours ago

Do you know the definition of insanity?

do you know software developers?

[-] deathmetal27@lemmy.world 2 points 2 hours ago

But did you get the reference?

[-] CameronDev@programming.dev 16 points 15 hours ago

How are you crashing your system?! Crashing program sure, but the entire system?

[-] sebsch@discuss.tchncs.de 17 points 14 hours ago

Try it out on your own system.

:(){
 :|:&
};:

It's totally possible

[-] CameronDev@programming.dev 9 points 14 hours ago* (last edited 14 hours ago)

Doesn't explain OPs task management example. And won't crash the kernel, just make things unresponsive

[-] bi_tux@lemmy.world 9 points 14 hours ago

it didn't crash the kernel, it just killed every process that isn't run by the root user, which kind of feels like a crash

[-] CameronDev@programming.dev 3 points 14 hours ago

Ah, that definitely would feel like a crash. Sent kill signal to cgroup accidentally? Or just iterate over all processes and signal them all?

[-] bi_tux@lemmy.world 4 points 13 hours ago* (last edited 13 hours ago)

probably the later, but idk how, all I did was insert a string in the following command like this:

``Command::new("bash")

.arg("-c") .arg(format!("ps -aux | grep -i "{}" | awk '{{print $2}}' | xagrs kill -9", input)

.output()

.expect("error");``

I've tested the command and it worked flawlessly in the terminal, but I have no idea what I'm doing, since I'm new to rust and never worked with this library

[-] CameronDev@programming.dev 4 points 13 hours ago

There are rust libraries to send signals, might be better to use those rather than calling bash. eg. https://docs.rs/nix/latest/nix/sys/signal/index.html

I'm guessing if input was "", then it would sigkill all processes? Less confident, but some functions behave slightly differently in an interactive console vs a non interactive, maybe ps has a different format when used non interactively?

Aside, you want three backticks and a newline to get code formatting :)
[-] bi_tux@lemmy.world 3 points 11 hours ago* (last edited 11 hours ago)

thx, btw I figured it out:

I forgot to trimm the string, so it had a line break in it which lead to grep showing the processes from the term I put in + all processes that contain a space/linebreak and appearently all processes shown by ps aux contain some kind of space (makes sense, since there are spaces between the user, pid, etc) so yeah, I ended up trying to kill every process on the system, but it only killed the user processes, since I ran everything without sudo

[-] n3cr0@lemmy.world 5 points 14 hours ago

rm -rf

Works for . current directory. Yay!

... also works for / system root. 🔥 Nay!

[-] CanadaPlus@lemmy.sdf.org 3 points 10 hours ago

Does it? I thought / specifically was protected, and you needed to add --no-preserve-root.

[-] CameronDev@programming.dev 2 points 14 hours ago

That won't crash your kernel, and I was more curious about the OPs example. Task management is basically reading some files, and sending signals, it should be near impossible to crash the system.

[-] kwozyman@lemmy.world 3 points 14 hours ago
[-] CameronDev@programming.dev 4 points 14 hours ago* (last edited 14 hours ago)

OPs example was task management, which doesn't require kernel modules.

this post was submitted on 20 Sep 2024
168 points (97.2% liked)

Programmer Humor

32063 readers
880 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS