Hide

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

OpenID
or
Sign in Register

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Hide

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

Make perl crash

Terminal - Make perl crash
perl -e '$x = []; push @$x, eval { $x = 1; return $x = 1; }'
2009-10-07 22:42:18
User: dstahlke
Functions: eval perl return
-2
Up
Down
Make perl crash

It is not easy to make perl give a segfault, but this does it. This is a known issue but apparently not easy to fix. This is completely useless except for showing people that perl is not bullet-proof.

Show sample output | Add to favourites | Report as malicious

Alternatives

There are 7 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

It's because of perl's liberal nature. It tries to let you get away with things you shouldn't. Read it's documentation; it states as a known bug that it doesn't enforce the warnings pragma.

Try it now, using pythonic-type scoping and you find that when you force it to only allow proper coding practices, no such failures occur:

perl -eMstrict '$x = []; push @$x, eval { $x = 1; return $x = 1; }'

Your statement is misleading. With more intellectual honesty you would have stated that 1) nothing is bullet proof, and 2) poor coding practices are especially vulnerable

Comment by linuxrawkstar 188 weeks and 5 days ago

What does "-eMstrict" do? With "-Mstrict -e" or "-e 'use strict; ...'" it still segfaults but with "-eMstrict" it doesn't. Google doesn't turn up anything on this option.

Comment by dstahlke 188 weeks and 4 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts