I believe the logic in this patch is inverted for generating that #define.
Kinsey
-Original Message-
From: devel On Behalf Of Sebastian Huber
Sent: Wednesday, July 13, 2022 06:42
To: devel@rtems.org
Subject: [PATCH] cdtest: Restrict exceptions during sysinit
Exceptions during system
On 14/7/2022 6:39 pm, Sebastian Huber wrote:
> I think the message is clear, applications should start their work in the
> initialization thread.
I have reviewed the test and yes I agree. The work can start in global
constrictors but they should work. I think C++ should be used very carefully
On 14/07/2022 10:33, Chris Johns wrote:
On 14/7/2022 4:08 pm, Sebastian Huber wrote:
On 14/07/2022 02:36, Chris Johns wrote:
Exceptions during system initialization work only on targets which do not need
a registration of exception frames during the global construction. In
particular,
On 14/7/2022 4:08 pm, Sebastian Huber wrote:
> On 14/07/2022 02:36, Chris Johns wrote:
>>> Exceptions during system initialization work only on targets which do not
>>> need
>>> a registration of exception frames during the global construction. In
>>> particular, targets which use the DWARF2
On 14/07/2022 02:36, Chris Johns wrote:
Exceptions during system initialization work only on targets which do not need
a registration of exception frames during the global construction. In
particular, targets which use the DWARF2 unwinder cannot use exceptions during
system initialization.
I
On 13/7/2022 9:41 pm, Sebastian Huber wrote:
> Exceptions during system initialization work only on targets which do not need
> a registration of exception frames during the global construction. In
> particular, targets which use the DWARF2 unwinder cannot use exceptions during
> system
Exceptions during system initialization work only on targets which do not need
a registration of exception frames during the global construction. In
particular, targets which use the DWARF2 unwinder cannot use exceptions during
system initialization.
---
testsuites/samples/cdtest/main.cc | 14
