<div dir="ltr"><div><div><div><div><div>Hi there!<br><br></div>While thinking about how it would be possible to implement various smart ptr related checkers I tried to review current state of MallocChecker and came up with that it would be great to have RegionState info available to other checkers. Could you please share your points of view and comments on the following statements / questions:<br><br></div>1. Is there any right way for chaining checkers? How they are expected to communicate between each other (excluding generation of nodes / ProgramStates). I've heard that there are couple of problems caused by inlining functions, constructors / descructors.<br></div>2. What do you think about moving RegionState to the Core of CSA or providing optional extended info in MemRegion about the source of such region (new opearator / array new, malloc, alloca, etc). So it would be available to all checkers.<br></div>3. Is there any roadmap for CSA and especially for dynamic memory management modeling & related checkers?<br><br></div>Regards, Alexey K<br clear="all"><div><div><div><div><div><div><div><div><div><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><a href="https://www.linkedin.com/profile/view?id=AAMAABn6oKQBDhBteiQnWsYm-S9yxT7wQkfWhSw" target="_blank">linkedin.com/profile</a><br><br><a href="http://github.com/alexeyknyshev" target="_blank">github.com/alexeyknyshev</a><span></span><a href="http:///" target="_blank"></a><span></span><br><a href="https://bitbucket.org/alexeyknyshev/" target="_blank">bitbucket.org/alexeyknyshev</a><br></div></div>
</div></div></div></div></div></div></div></div></div></div>