In C I’m aware that an array index out of bounds will produce a segmentation fault. Is it the same for a stack overflow in C and there will also be a segmentation fault i.e. same error type for a similar problem?

C中無法保證會(huì)出現(xiàn)分段錯(cuò)誤. C標(biāo)準(zhǔn)說它是undefined behaviour并且保留它.它可能表現(xiàn)出來,取決于實(shí)現(xiàn)/平臺(tái).

Or is it sometimes something much worse and a stack overflow in C could cause an operating system failure and force you to power cycle to get back? Or even worse, cause irreversible hardware damage? How bad effects can a stack overflow mistake have?

在現(xiàn)代操作系統(tǒng)中,很少有任何不幸發(fā)生在系統(tǒng)上;通常,只有程序會(huì)崩潰.現(xiàn)代操作系統(tǒng)使用various memory protection techniques.

It seems clear that the protection is better in Java than in C. Is it any better in C than in assembly / machine code or is it practically the same (lack of) protection in C as a assembly?

那是因?yàn)樵贘ava中,內(nèi)存是“被管理的”.在C中,它留給程序員;這是設(shè)計(jì)的. C編譯器最終生成機(jī)器代碼;所以它不會(huì)更好或更糟.明顯,

一個(gè)好的編譯器可以檢測(cè)到其中的一些問題并警告你,這與C語言相比,與匯編相比具有優(yōu)勢(shì).

總結(jié)

以上是生活随笔為你收集整理的java中堆栈溢出_java – 由于堆栈溢出,C中通常会发生什么？的全部?jī)?nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯(cuò)，歡迎將生活随笔推薦給好友。