That's like saying all bugs are undefined behavior. C lets you write to your own... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		halpmeh on Nov 28, 2022 \| parent \| context \| favorite \| on: Everything I wish I knew when learning C That's like saying all bugs are undefined behavior. C lets you write to your own stack, so if you corrupt the stack due to an application error (e.g. bounds check), then that's just a bug because you were executing fully-defined behavior. Examples of undefined behavior would be things like dividing by 0 where the result of that operation can differ across platforms because the specific behavior wasn't defined in the language spec.

kllrnohj on Nov 28, 2022 [–]

Writing past the end of an array is defined as UB.

Not all bugs are UB, you can have logic errors of course. But stack corruption is I believe always triggered by UB.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact