I’m porting a program that when I run stops with the message:
“Abort”.
I’ve been able to figure out that this is the result of an abort signal.
However I cannot find where in the source that signal is generated.
I’m starting to thing it’s somewhere in the c/c++ lib, is that
possible.
“Mario Charest” <mcharest@clipzinformatic.com> wrote in message
news:9o7ne4$jaf$1@inn.qnx.com…
I’m porting a program that when I run stops with the message:
“Abort”.
I’ve been able to figure out that this is the result of an abort signal.
However I cannot find where in the source that signal is generated.
I’m starting to thing it’s somewhere in the c/c++ lib, is that
possible.
Found it, it was an exception being thrown ;-( I’ve added -fexceptions
to both compile and link steps but I still get Abort instead of having
the exception being catch. What else have I miss?
Mario Charest <mcharest@clipzinformatic.com> wrote:
Found it, it was an exception being thrown ;-( I’ve added -fexceptions
to both compile and link steps but I still get Abort instead of having
the exception being catch. What else have I miss?
Abort() is the default behaviour for an unhandled exception. Simply
adding the -fexceptions flag only tells the compiler to genereate
exception frame code (which is always on for Dinkum libs). Perhaps
you could setup some catch/throw blocks in you main to handle/examine
what the exception is you’re throwing.
-Adam
amallory@qnx.com
Make sure that when you link you are telling qcc that it is a C++ app
(either pass -lang-c++ or use QCC)
This pulls in the correct exception handling gunk that is needed.
Operating System for Tech Supp <os@qnx.com> wrote:
Mario Charest <> mcharest@clipzinformatic.com> > wrote:
Found it, it was an exception being thrown ;-( I’ve added -fexceptions
to both compile and link steps but I still get Abort instead of having
the exception being catch. What else have I miss?
Abort() is the default behaviour for an unhandled exception. Simply
adding the -fexceptions flag only tells the compiler to genereate
exception frame code (which is always on for Dinkum libs). Perhaps
you could setup some catch/throw blocks in you main to handle/examine
what the exception is you’re throwing.
-Adam
amallory@qnx.com
–
cburgess@qnx.com
“Colin Burgess” <cburgess@qnx.com> wrote in message
news:9o88vt$p8a$1@nntp.qnx.com…
Make sure that when you link you are telling qcc that it is a C++ app
(either pass -lang-c++ or use QCC)
I’ve added it to compile option but not to link stage. That was it.