Timeline for Shortest code that raises a SIGSEGV
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2020 at 9:04 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jun 17, 2020 at 3:13 | comment | added | absoluteAquarian | Fair enough. Though, you could've explained that in a way without trying to use a strawman like "Fish can swim; I can swim, so I am a fish." | |
| Jun 17, 2020 at 1:06 | comment | added | Sapphire_Brick | You seem to be saying "Fish can swim; I can swim, so I am a fish.". A segmentation fault is more specific than the definition you gave. It has to be the signal SIGSEGV, not just any memory permission error. Suppose you try to use a bash command that you don't have permission to use. Is that a segmentation fault? Of course not. | |
| Jun 17, 2020 at 0:53 | comment | added | absoluteAquarian | @Sapphire_Brick It most definitely is. "A segmentation fault occurs when a program attempts to access a memory location that it is not allowed to access, or attempts to access a memory location in a way that is not allowed (for example, attempting to write to a read-only location, or to overwrite part of the operating system)." (source) Archived data can't be accessed in TI-BASIC, simple as that. Do your research before commenting next time. | |
| Jun 11, 2020 at 14:45 | comment | added | Sapphire_Brick | It's not a segmentation fault. | |
| Apr 26, 2019 at 13:49 | history | answered | absoluteAquarian | CC BY-SA 4.0 |