> If you have 39 tasks in Runnable state, I guess that they are not all
> blocked in libc read ?
> So, you might investigate which task(s) are really still doing something
> by doing e.g.
>thread apply all bt
> and/or put breakpoints at places that you know should be soon
> encountered
> by the
On Thu, 2017-12-07 at 12:39 +, Silva João wrote:
> > If you have 39 tasks in Runnable state, I guess that they are not all
> > blocked in libc read ?
> > So, you might investigate which task(s) are really still doing something
> > by doing e.g.
> >thread apply all bt
> > and/or put breakpoi
valgrind report memory as being reachable when I think it has been properly
freed in the below program. Is this a bug, a feature, a misunderstanding of
how to use delete by me?
Thanks
Yusuf
===
#include
using namespace std;
int test() {
int* p = new int[5];
delete []
