Mmm I see this meeting was cancelled on Jan 11....am I wrong?

Yes, to be more pragmatic let's for example look at the bugs reported against the glibc malloc component (pointing to the glibc just because I am more familiar with it compared to the other library ex

IMO we should initially spawn an investigation task trying to work on one or few specific issues and, once we have a better view of the value the WG can and will provide, we can come back with a more

Hi Lukas Can you specify what you mean by "known issue"? IMO it is a bit vague. For example if you mean bug I could think of the kernel bugzilla (https://bugzilla.kernel.org/), if you mean static chec

Hi All On my side I am fully supportive of Elana's goals and, WRT to these goals. I think that what Paul pointed out in the email below is the basis to achieve such goals. Thanks Gab

Hi Alex I also agree with the summary that Lukas gave here. From my experience the safety system are always guarded by an external flow monitor (e.g. a watchdog) that triggers in case the safety relev

Looks good to me too Gab

From my perspective I would go for 5. Right now I don't have other names suggestions Regards Gab

Yes agreed Sorry, I replied to Paul and missed the follows up from Elana and Jochen. However I also think it is a good topic to elaborate on. Thanks Gab

Hi All Given that the topic was presented in a micro conference the deck was intended to trigger an open discussion rather than showing results. I agree with everything that Paul wrote down below and

Congratulations Shuah Well deserved! Looking forward to even more contributions to come. Thanks Gab

Hi All Today I would not be available to take the call as I am on vacation however WRT the above mentioned papers I am ok with publishing the content (not sure if there are cosmetic or license adjustm