| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Matthias Schmitt <freak002(at)mmp(dot)lu> |
| Subject: | Re: OSX doesn't accept identical source/target for strcpy() anymore |
| Date: | 2013-10-28 19:20:20 |
| Message-ID: | 526EB8F4.2070806@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 10/28/2013 02:26 PM, Andres Freund wrote:
>
> It'd be neat if we could get a buildfarm animal up that uses valgrind -
> which would catch such and lots of other errors. That's where the topic
> has come up in the past:
> http://www.postgresql.org/message-id/20110312133224.GA7833%40tornado.gateway.2wire.net
> http://www.postgresql.org/message-id/20130217142209.GA5073@awork2.anarazel.de
>
How exactly is it going to do that?
Fundamentally, the buildfarm client is simply glue to run existing build
and test code, collect the results, and send them to the server. AFAICT
there are no configure or make targets for running under valgrind.
If someone provides the requisite support in the build system for this
I'll be happy to add buildfarm support for it.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-10-28 19:25:16 | Re: Darwin: make check fails with "child process exited with exit code 134" |
| Previous Message | didier | 2013-10-28 18:44:12 | Re: OSX doesn't accept identical source/target for strcpy() anymore |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-10-28 19:25:16 | Re: Darwin: make check fails with "child process exited with exit code 134" |
| Previous Message | Andres Freund | 2013-10-28 19:11:41 | Re: Detection of nested function calls |