Cygwin and stdexcept bug ?

["Pavel Fedin" <p dot fedin at samsung dot com>]

 Hello everyone!

 On Linux if a C++ application throws uncaught error, there's explanation given:
--- cut ---
terminate called after throwing an instance of 'std::runtime_error'
  what():  Just throw up
Aborted
--- cut ---

 On 64-bit Cygwin the same code simply silently aborts, giving no hints. I've tried on 32 bits; everything seems to work. However i
haven't updated my 32-bit install for ages; may be something has changed.
 Is it a bug or feature?

 My test code is:
--- cut ---
#include <stdexcept>
#include <iostream>

int main(void)
{
  throw std::runtime_error("Just throw up");
  std::cout << "What ???\n";
  return 0;
}
--- cut ---

Kind regards,
Pavel Fedin
Senior Engineer
Samsung Electronics Research center Russia



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple