Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c++ > #7809

Re: exception problem with cygwin - terminate called recursively

From Philipp Kraus <philipp.kraus@flashpixx.de>
Newsgroups comp.lang.c++
Subject Re: exception problem with cygwin - terminate called recursively
Date 2011-07-14 17:48 +0200
Organization 1&1 Internet AG
Message-ID <ivn348$hff$1@online.de> (permalink)
References <ivmv25$e8v$1@online.de> <c4bbbd02-a36b-4090-9155-80b536e9fc72@glegroupsg2000goo.googlegroups.com>

Show all headers | View raw


On 2011-07-14 17:11:25 +0200, peter koch said:

> It seems to me that your exception either has no corresponding catch 
> clause or that it is thrown when another exception is active: this 
> causes std::terminate to be called.

on the main program the exception should be catched like:

myclass {
   mymethod() {
       if something
             mymethod()

       throw exception
  }
}

main() {
   myclass x;
   try {
       x.mymethod()
  } catch (...) {}

}

In my optinion I think if I throw an exception the complete runing 
process would be breaked down and the exception is send to the main 
program, if there is a try-catch the exception is be handled, if not 
the program terminates. I don't use any threads. I don't understand why 
Windows should be handle the exception in another way than Linux and 
OSX !?

Thanks for your answer

Phil

Back to comp.lang.c++ | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

Re: exception problem with cygwin - terminate called recursively peter koch <peter.koch.larsen@gmail.com> - 2011-07-14 08:11 -0700
  Re: exception problem with cygwin - terminate called recursively Philipp Kraus <philipp.kraus@flashpixx.de> - 2011-07-14 17:48 +0200

csiph-web