This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 08/22/2011 09:33 AM, Andrew Haley wrote: > On 08/21/2011 11:02 PM, sudhakar govindavajhala wrote: > >> Is there a flag in compiling or using gcc/g++ so that a signal like >> SIGSEGV in my C++ program will result in an exception being thrown? >> If not, why not? I mean, is this is not a reasonable expectation in >> OOPS? >> >> Is there anything I need to be careful in throwing an exception in my >> signal handlers that convert SIGSEGV to an exception. I will ensure >> that no malloc style calls are called. > > There is gcc support for this on most of the GNU/Linux platforms, but it's > not so well supported elsewhere. The answer to your question depends on > your platform. Like this: zebedee:~ $ g++ segv.c -g -lpthread -Wall -fnon-call-exceptions -O2 zebedee:~ $ ./a.out Hello! Andrew.
Attachment:
segv.c
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |