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

Groups > comp.lang.c++ > #7807 > unrolled thread

Re: exception problem with cygwin - terminate called recursively

Back to article view | Back to comp.lang.c++

Contents

  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

#7807 — Re: exception problem with cygwin - terminate called recursively

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.
That is only a guess, though. You should reduce your code to a minimal sample demonstrating the problem, then you can show it here.

Peter

[toc] | [next] | [standalone]

#7809

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

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.c++

csiph-web