Timeline for Why would accessing uninitialized memory necessarily be undefined behavior?
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 26 at 21:48 | comment | added | marbens |
No it isn't necessarily undefined behavior, memory allocated with malloc and realloc can be read from without being initialized without causing undefined behavior as long as you are using a type with no trap representations.
|
|
| Sep 30, 2023 at 22:46 | vote | accept | CPlus | ||
| Sep 14, 2023 at 11:45 | comment | added | Martin Kealey | see answer below | |
| Sep 8, 2023 at 21:25 | answer | added | Peter - Reinstate Monica | timeline score: 4 | |
| Sep 8, 2023 at 0:18 | comment | added | CPlus | @MartinKealey My question was more: why was it necessary for them to not define the behavior? | |
| Sep 7, 2023 at 20:03 | answer | added | supercat | timeline score: 2 | |
| Sep 7, 2023 at 18:36 | answer | added | Martin Kealey | timeline score: 4 | |
| Sep 7, 2023 at 18:04 | comment | added | Martin Kealey | Why is the word "necessarily" in the title of this question? The nature of "undefined" means that's not necessarily anything in particular. | |
| Sep 7, 2023 at 17:22 | answer | added | Matthieu M. | timeline score: 8 | |
| Sep 7, 2023 at 15:30 | answer | added | Barmar | timeline score: 6 | |
| Sep 7, 2023 at 10:28 | answer | added | jpa | timeline score: 9 | |
| Sep 7, 2023 at 2:39 | history | became hot network question | |||
| Sep 6, 2023 at 22:51 | answer | added | Pseudonym | timeline score: 29 | |
| Sep 6, 2023 at 22:02 | answer | added | occipita | timeline score: 13 | |
| Sep 6, 2023 at 21:52 | answer | added | Michael Homer♦ | timeline score: 22 | |
| Sep 6, 2023 at 19:48 | answer | added | kaya3 | timeline score: 20 | |
| Sep 6, 2023 at 18:38 | history | asked | CPlus | CC BY-SA 4.0 |