Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with stack
Search options not deleted
user 14120
For challenges involving stack-like data structures (see tag wiki for details), including interpreters of stack-based programming languages and challenges specifically about call stacks.
3
votes
Weirdest way to produce a stack overflow
Ruby
evil = "eval evil"
eval evil
This will cause SystemStackError: stack level too deep
1.9.3p448 :006 >
1.9.3p448 :007 > evil = " eval evil"
=> " eval evil"
1.9.3p448 :008 > eval evil
SystemStackError … : stack level too deep
from /usr/local/rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/irb/workspace.rb:80
Maybe IRB bug! …
- 241