Re: Fix runtime errors from -fsanitize=undefined

From: Raúl Marín Rodríguez <rmrodriguez(at)carto(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix runtime errors from -fsanitize=undefined
Date: 2019-07-05 16:38:37
Message-ID: CAM6_UM7FD_JeY6Y2=nCB=i8WPk07Tw8ph0WSpsazB3UtovEAfw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> This sanitizer has found real problems in the past. By removing these
> trivial issues we can then set up a build farm animal or similar to
> automatically check for any new issues.

We have done exactly this in postgis with 2 different jobs (gcc and clang)
and, even though it doesn't happen too often, it's really satisfying when
it detects these issues automatically.

--
Raúl Marín Rodríguez
carto.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexey Bashtanov 2019-07-05 16:40:49 Re: log bind parameter values on error
Previous Message Tom Lane 2019-07-05 16:38:02 Re: [PATCH v4] Add \warn to psql