| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Valgrind Memcheck support |
| Date: | 2013-09-11 03:32:03 |
| Message-ID: | 20130911033203.GC225735@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 06, 2013 at 09:55:09PM +0100, Greg Stark wrote:
> On Sun, Jun 9, 2013 at 10:25 PM, Noah Misch <noah(at)leadboat(dot)com> wrote:
> > - Memcheck has support for detecting leaks. I have not explored that
> > side at
> > all, always passing --leak-check=no. We could add support for freeing
> > "everything" at process exit, thereby making the leak detection
> > meaningful.
> >
>
> I think this is missing the type of leaks we actually care about. The way
> palloc works we can be virtually certain that if we did that we wouldn't
> have any leaks. All it would detect are the random one-off mallocs we know
> very well are there.
Probably so; it's not too promising.
--
Noah Misch
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2013-09-11 03:33:41 | Weaker shmem interlock w/o postmaster.pid |
| Previous Message | Noah Misch | 2013-09-11 02:45:05 | Re: Pending query cancel defeats SIGQUIT |