Re: Workspace Initialization Faliure Bug

2021-10-01 Thread Joel Sherrill
On Fri, Oct 1, 2021, 12:10 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 01/10/2021 16:27, Joel Sherrill wrote: > > > > > > On Fri, Oct 1, 2021, 8:42 AM Sebastian Huber > > > > wrote: > > > > On 01/10/2021 00:38, Joel Sherrill

Re: Workspace Initialization Faliure Bug

2021-10-01 Thread Sebastian Huber
On 01/10/2021 16:27, Joel Sherrill wrote: On Fri, Oct 1, 2021, 8:42 AM Sebastian Huber > wrote: On 01/10/2021 00:38, Joel Sherrill wrote: > I think in this configuration, the workspace is essentially unneeded > but has to be able to be

Re: Workspace Initialization Faliure Bug

2021-10-01 Thread Joel Sherrill
On Fri, Oct 1, 2021, 8:42 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 01/10/2021 00:38, Joel Sherrill wrote: > > I think in this configuration, the workspace is essentially unneeded > > but has to be able to be initialized. It shows that the static > > allocation work has

Re: Workspace Initialization Faliure Bug

2021-10-01 Thread Sebastian Huber
On 01/10/2021 00:38, Joel Sherrill wrote: I think in this configuration, the workspace is essentially unneeded but has to be able to be initialized. It shows that the static allocation work has succeeded in trimming the workspace at least. But now we have to account for an empty one. :) Did you

Workspace Initialization Faliure Bug

2021-09-30 Thread Joel Sherrill
Hi I need to produce a small test case but on the way to realizing the IDLE task stacks needed to be allocated special, I tripped across a problem where the computed workspace needed size was so low, it tripped the second condition in the error check in _Heap_Get_first_and_last_block: if ( h