Custom error message for stack overflow in C++

[FlatAssembler]

Hey, guys!
So, there is a bug in the compiler for my programming language, written in C++, that results in a Stack Overflow error: https://github.com/FlatAssembler/AECforW...y/issues/5
I am interested whether I can, until I find a way fix it (I have not even diagnosed it exactly yet), at least provide a custom error message when it happens, which is informative (that the error does not seem to occur if it is compiled with GCC or if optimizations are enabled in CLANG) and links to the issue on GitHub. You can easily provide custom error messages using C signals (parts of the C++ standard library) in case of Segmentation Fault or Division by Zero Error, however, to my surprise, there does not seem to be an easy way to give a custom error messages in case of Stack Overflow error.

[Foxaèr]

It's the admin punishing us for our insolence.

[FlatAssembler]

It's the admin punishing us for our insolence.

I have no idea what you are talking about.

[BrianSoddingBoru4]

It's the admin punishing us for our insolence.

I have no idea what you are talking about.

It’s a little case of butthurt. It’ll clear up.

Boru

[HappySkeptic]

Hey, guys!
So, there is a bug in the compiler for my programming language, written in C++, that results in a Stack Overflow error: https://github.com/FlatAssembler/AECforW...y/issues/5
I am interested whether I can, until I find a way fix it (I have not even diagnosed it exactly yet), at least provide a custom error message when it happens, which is informative (that the error does not seem to occur if it is compiled with GCC or if optimizations are enabled in CLANG) and links to the issue on GitHub. You can easily provide custom error messages using C signals (parts of the C++ standard library) in case of Segmentation Fault or Division by Zero Error, however, to my surprise, there does not seem to be an easy way to give a custom error messages in case of Stack Overflow error.

A quick google search (on the site stackoverflow) suggests it is possible in Windows, but very difficult.

A stack overflow is usually a fatal error for a thread.

In your case, it is probably caused by an infinite recursive loop (or you have too small a stack set).  You need to fix that by perhaps checking your recursion depth and erroring out before the overflow, or else just fixing your compiler.

[FlatAssembler]

Hey, guys!
So, there is a bug in the compiler for my programming language, written in C++, that results in a Stack Overflow error: https://github.com/FlatAssembler/AECforW...y/issues/5
I am interested whether I can, until I find a way fix it (I have not even diagnosed it exactly yet), at least provide a custom error message when it happens, which is informative (that the error does not seem to occur if it is compiled with GCC or if optimizations are enabled in CLANG) and links to the issue on GitHub. You can easily provide custom error messages using C signals (parts of the C++ standard library) in case of Segmentation Fault or Division by Zero Error, however, to my surprise, there does not seem to be an easy way to give a custom error messages in case of Stack Overflow error.

A quick google search (on the site stackoverflow) suggests it is possible in Windows, but very difficult.

A stack overflow is usually a fatal error for a thread.

In your case, it is probably caused by an infinite recursive loop (or you have too small a stack set).  You need to fix that by perhaps checking your recursion depth and erroring out before the overflow, or else just fixing your compiler.

How can you check for the recursion depth? And how do you check how much stack space is left? Are those things even possible in standard C++?

Do you have some idea why that error would occur on CLANG and Visual Studio C++ but not on GCC?

[zebo-the-fat]

Out of cheese error?

[Angrboda]

Try hitting it with a hammer.

[FlatAssembler]

Try hitting it with a hammer.

To hit what with a hammer? The problem occurs on whatever computer my program, if compiled using CLANG without optimization or Visual Studio C++, is run on.

---

Out of cheese error?

I am not sure what you mean.

[arewethereyet]

Try hitting it with a hammer.

I think this step comes after turning it off and back on.