[Pspp-commits] [SCM] GNU PSPP branch, master, updated. v1.4.1-196-ge333a44

[Ben Pfaff]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU PSPP".

The branch, master has been updated
       via  e333a444bba7a84682b26a68c0894a8ca4f353a4 (commit)
       via  be53a7a37e9159dfd7e629e92b08c708d339f162 (commit)
       via  cb3c3f916a0ef91a758aa3b6795ad8fb038d00af (commit)
       via  35cf05a2036e9c3562d275ed812059dd7b2b5d01 (commit)
       via  0a179d09848bfd8776833071f496e095c7b60d74 (commit)
      from  6c8b13da57b074620495a0543bd7944bca574a42 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit e333a444bba7a84682b26a68c0894a8ca4f353a4
Author: Ben Pfaff <blp@cs.stanford.edu>
Date:   Fri Dec 25 12:14:38 2020 -0800

    cairo-pager: Add outline to PDF output.

commit be53a7a37e9159dfd7e629e92b08c708d339f162
Author: Ben Pfaff <blp@cs.stanford.edu>
Date:   Fri Dec 25 21:54:48 2020 -0800

    cairo: Avoid using cairo_t for a destroyed cairo_surface_t.
    
    xr_pager_destroy() would destroy the latest cairo_t, if there was one.
    Generally there wasn't, since in the common case it got destroyed by
    xr_pager_run() when the fsm emptied out, but in the case of the last page
    in a produced output file, xr_destroy() would call xr_pager_destroy()
    after first destroying the surface_t it was drawing on.  I don't think this
    is an actual bug, because everything is properly reference-counted inside
    Cairo (the cairo_t holds a reference on its cairo_surface_t) but I found it
    confusing.

commit cb3c3f916a0ef91a758aa3b6795ad8fb038d00af
Author: Ben Pfaff <blp@cs.stanford.edu>
Date:   Fri Dec 25 21:55:57 2020 -0800

    doc: Suppress fontconfig warnings from Leak Sanitizer running pspp-output.
    
    Otherwise building the docs fails if one builds with Address Sanitizer or
    Leak Sanitizer.

commit 35cf05a2036e9c3562d275ed812059dd7b2b5d01
Author: Ben Pfaff <blp@cs.stanford.edu>
Date:   Fri Dec 25 16:22:14 2020 -0800

    Fix memory leaks reported by Address Sanitizer.

commit 0a179d09848bfd8776833071f496e095c7b60d74
Author: Ben Pfaff <blp@cs.stanford.edu>
Date:   Fri Dec 25 21:56:53 2020 -0800

    Add more Valgrind leak report suppressions.
    
    These leaks seem unavoidable and they are not worth reporting.
    
    Valgrind still reports a lot of leaks that I haven't determined to either
    be fixable or unavoidable.

-----------------------------------------------------------------------

Summary of changes:
 NEWS                               |   3 +
 doc/automake.mk                    |   2 +-
 doc/invoking.texi                  |   9 +++
 src/libpspp/i18n.c                 |   4 +-
 src/output/cairo-pager.c           | 141 +++++++++++++++++++++++++++++++++++--
 src/output/cairo-pager.h           |   5 ++
 src/output/cairo.c                 |  42 +++++++----
 src/output/options.c               |  19 ++---
 src/output/pivot-table.c           |  13 ++--
 src/output/spv-driver.c            |   8 ++-
 src/output/spv/spv-light-decoder.c |   1 +
 tests/valgrind.supp                |  39 ++++++++++
 12 files changed, 246 insertions(+), 40 deletions(-)


hooks/post-receive
-- 
GNU PSPP