> Can you catch the exception with "catch (...)"?
I tried this route and added such catch-all clause just at the throw
site. Moreover, I put an explicit throw("catch-me") there in hope to
see if it wil just get caught rightaway. Nope, the exception is thrown
properly, but the catch (...) is not in
On Wed, 8 Apr 2020 at 10:14, krokus via cfe-users
wrote:
> Richard,
>
> Thanks for the quick response; it gave me some directions to
> investigate further, otherwise it seemed I got stuck trying to make
> sense of many moving pieces in this puzzle. So, my understanding is
> that generally the run
Richard,
Thanks for the quick response; it gave me some directions to
investigate further, otherwise it seemed I got stuck trying to make
sense of many moving pieces in this puzzle. So, my understanding is
that generally the run-time exception handling should _not_ depend on
the order of the link
On Sun, 5 Apr 2020 at 15:31, krokus via cfe-users
wrote:
> First of all a preface - This problem was spotted while trying to
> build a large C++ project which links a close to 100 of object file
> together, plus libraries. I can't replicate this behavior in a simple
> isolated test. Just want to
First of all a preface - This problem was spotted while trying to
build a large C++ project which links a close to 100 of object file
together, plus libraries. I can't replicate this behavior in a simple
isolated test. Just want to understand if potentially this may be
caused by clang's compiler or
