Hi, On 2016-03-07 17:39:30 -0800, Andres Freund wrote: > I'm setting up a buildfarm animal that runs under valgrind.
Which is now running as 'skink'. The first failed due to a missing trick in the wrapper script, but the second one looks like it had a legit issue: http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=skink&dt=2016-03-08%2004%3A22%3A00 ==1827== Invalid write of size 4 ==1827== at 0x14E35DD1: plperl_ref_from_pg_array (plperl.c:1459) ==1827== by 0x14E3608C: plperl_call_perl_func (plperl.c:2135) ==1827== by 0x14E3C24F: plperl_func_handler (plperl.c:2357) ==1827== by 0x14E3C24F: plperl_call_handler (plperl.c:1778) ==1827== by 0x5E0531: ExecMakeFunctionResultNoSets (execQual.c:2041) ==1827== by 0x5E641C: ExecTargetList (execQual.c:5367) ==1827== by 0x5E641C: ExecProject (execQual.c:5582) ==1827== by 0x5FC1C1: ExecResult (nodeResult.c:155) ==1827== by 0x5DF577: ExecProcNode (execProcnode.c:392) ==1827== by 0x5DB675: ExecutePlan (execMain.c:1566) ==1827== by 0x5DB675: standard_ExecutorRun (execMain.c:338) ==1827== by 0x6F4DD7: PortalRunSelect (pquery.c:942) ==1827== by 0x6F631D: PortalRun (pquery.c:786) ==1827== by 0x6F2FFA: exec_simple_query (postgres.c:1094) ==1827== by 0x6F2FFA: PostgresMain (postgres.c:4021) ==1827== by 0x46D33F: BackendRun (postmaster.c:4258) ==1827== by 0x46D33F: BackendStartup (postmaster.c:3932) ==1827== by 0x46D33F: ServerLoop (postmaster.c:1690) ==1827== Address 0x15803220 is 304 bytes inside a block of size 8,192 alloc'd ==1827== at 0x4C28BB5: malloc (vg_replace_malloc.c:299) ==1827== by 0x808A37: AllocSetAlloc (aset.c:864) ==1827== by 0x80A3B3: palloc (mcxt.c:907) ==1827== by 0x7E0802: get_func_signature (lsyscache.c:1483) ==1827== by 0x14E367D6: plperl_call_perl_func (plperl.c:2116) ==1827== by 0x14E3C24F: plperl_func_handler (plperl.c:2357) ==1827== by 0x14E3C24F: plperl_call_handler (plperl.c:1778) ==1827== by 0x5E0531: ExecMakeFunctionResultNoSets (execQual.c:2041) ==1827== by 0x5E641C: ExecTargetList (execQual.c:5367) ==1827== by 0x5E641C: ExecProject (execQual.c:5582) ==1827== by 0x5FC1C1: ExecResult (nodeResult.c:155) ==1827== by 0x5DF577: ExecProcNode (execProcnode.c:392) ==1827== by 0x5DB675: ExecutePlan (execMain.c:1566) ==1827== by 0x5DB675: standard_ExecutorRun (execMain.c:338) ==1827== by 0x6F4DD7: PortalRunSelect (pquery.c:942) ==1827== I've now added configuration to valgrind so it wraps VALGRINDERROR-BEGIN / VALGRINDERROR-END around errors, to make the logs easier to search. Greetings, Andres Freund -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers