Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Challenges

Bytes to Segfault

+9
−0

Challenge

Cause the currently running program to receive the SIGSEGV signal (on Linux or other *nix systems) as fast as possible. What it does with the signal doesn't matter as long as it receives it.

This is code golf, smallest answer in each language wins. Some languages will have a tougher time than others. Keep in mind that if you depend on uninitalized data, it needs to always result in a segfault; a 0.000001% chance to not work invalidates your solution.

Example program

#include <stddef.h>
#include <stdio.h>

int main() {
    int* ohno = NULL;
    printf("%d", *ohno);
}
History

0 comment threads

12 answers

+12
−0

C, 5 bytes

main;

This exploits the fact that uninitialised globals live in the .bss section, and that section is not executable. So any attempt to execute code there, regardless of content, will cause a segfault.

History

1 comment thread

General comments (2 comments)
+7
−0

Python 2, 13 bytes

exec'+1'*5**9

Try it online!

No idea why this works. Something in the Python expression parser?

History

1 comment thread

General comments (2 comments)
+4
−0

Bash, 11

kill -11 $$

Try it online!

History

0 comment threads

+3
−0

Rust 1.0.0, 58 53 52 37 bytes

fn a(){#[no_mangle]static mmap:u8=0;}
History

0 comment threads

+2
−0

JavaScript (Node.js), 35 32 25 bytes

-7 bytes thanks to @celtschk‭

with(process)kill(pid,11)

Try it online!

History

1 comment thread

General comments (1 comment)
+2
−0

C, 16 bytes

m(){*(int*)m=0;}

Try it Online!

History

1 comment thread

General comments (1 comment)
+2
−0

x86 machine code, 3 bytes

31 FF AB

Try it online!

In assembly:

	xor edi, edi
	stosd

Set EDI to 0 by XORing it with itself, then use the 1-byte stosd instruction to try to write EAX to that address while advancing EDI.

History

0 comment threads

+1
−0

C (compliant), 19 bytes

(gcc -std=c18 -pedantic-errors)

int main(){main();}

Godbolt

History

0 comment threads

+1
−0

Ruby, 14 bytes

`kill -11 #$$`

Try this online!

History

0 comment threads

+0
−0

Python, 123 bytes

I'm just happy I got python to segfault :) there must be a better way to golf this.

a=lambda:0;e=tuple()
b=type(a.__code__)(0,0,0,0,0,0,(lambda x:x).__code__.co_code,e,e,e,'','','',0,b'',b'')
type(a)(b,{})()

Attempt This Online!

History

0 comment threads

+0
−0

Swift 5.4, 17 bytes

func f(){f()};f()

Pretty simple. It just calls itself until it stack overflows. You need to compile and run it, not just do it in the REPL, because the REPL just drops you back into the interpreter once it overflows.

It gives a warning "all paths through this function will call itself", but eh who cares?

History

0 comment threads

+0
−0

Rust, 47 bytes

fn main(){unsafe{print!("{}",*(0 as*mut i8));}}

Try it online!

History

0 comment threads

Sign up to answer this question »