Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I was having a very weird segfault that I eventually fixed today. It seems the problem was I was allocating a very large array on stack and that was causing the problem.
My question is, do you always get a SEGV signal on stack overflow? Is there any special signal that could alert there is a stack overflow problem?
I’m using g++ along with gdb.
The “signal” in the sense of Unix signals is apparently SEGV. 🙂 If you mean signal like using a diagnostic tool that will tell you when something bad is happening, you could try valgrind, but really, your system just told you. And knowing at compile time whether the stack will be overflowed is not possible, partly because the stack size limit is a runtime parameter, and besides I imagine if you knew what it would be a priori, you’d still be stuck with something like the Halting Problem.