[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Pspp-commits] [SCM] GNU PSPP branch, master, updated. v1.0.1-247-g5cfa8

From: Ben Pfaff
Subject: [Pspp-commits] [SCM] GNU PSPP branch, master, updated. v1.0.1-247-g5cfa87e
Date: Mon, 24 Sep 2018 01:51:48 -0400 (EDT)

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  5cfa87e44dab622b1f3f2312f9c41dd522210335 (commit)
       via  e0f9210e814d03bc43b6a9b30a402e403d5666b9 (commit)
       via  89198b80bfd7e3893ed7499ba25b9bf94faaffb9 (commit)
       via  a02c8c084678a90529038bea3ce4bd6ca3ce80fe (commit)
      from  812d0f700694bad063545e67186172bed6ebcfc0 (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 5cfa87e44dab622b1f3f2312f9c41dd522210335
Author: John Darrington <address@hidden>
Date:   Sun Sep 23 15:02:35 2018 +0200

    Dataset and PsppireDict to have their own copy of struct dictionary

commit e0f9210e814d03bc43b6a9b30a402e403d5666b9
Author: Ben Pfaff <address@hidden>
Date:   Sun Sep 23 20:42:07 2018 -0700

    lexer: Add support for embedded \0 bytes and missing trailing new-line.
    The lexer, at a low level, has not supported \0 bytes in the input stream
    because it used such a byte as the end-of-input indicator.  This caused
    some awkwardness for the higher-level lexer, which had to remove and flag
    \0 bytes as it read them.  This caused a bug in the higher-level lexer,
    which raised an error for each \0 byte it removed but did so when the
    lexer was in an intermediate state, which could read uninitialized data.
    This commit fixes the problem by adding support for \0 bytes to the
    low-level lexer (segmenter).  At the same time, it adds support for input
    that doesn't end in a new-line character.
    Bug #54664.
    Thanks to Tianxiao Gu for reporting this bug.

commit 89198b80bfd7e3893ed7499ba25b9bf94faaffb9
Author: Ben Pfaff <address@hidden>
Date:   Sun Sep 23 20:26:28 2018 -0700

    DO REPEAT: Avoid relying on null terminators.
    find_dummy_var() currently relies on the string passed in to have a null
    terminator (even though it accepts a length).  This is safe in the current
    tree but an upcoming commit will not ensure that it is null-terminated, so
    this commit removes the dependency.

commit a02c8c084678a90529038bea3ce4bd6ca3ce80fe
Author: Ben Pfaff <address@hidden>
Date:   Sun Sep 23 19:36:22 2018 -0700

    command-name: Avoid read past end of input buffer in find_word().
    When the input substring S is not null-terminated, find_word() could read
    past its end looking for a non-digit.  This fixes the problem.


Summary of changes:
 src/data/dataset.c                  |   3 +-
 src/language/control/repeat.c       |  18 +-
 src/language/lexer/command-name.c   |   2 +-
 src/language/lexer/lexer.c          |  38 +--
 src/language/lexer/lexer.h          |   1 +
 src/language/lexer/scan.c           |   9 +-
 src/language/lexer/scan.h           |   2 +-
 src/language/lexer/segment.c        | 665 ++++++++++++++++++++----------------
 src/language/lexer/segment.h        |   2 +-
 src/ui/gui/psppire-dict.c           |   8 +-
 tests/language/lexer/       |  17 +-
 tests/language/lexer/scan-test.c    |  29 +-
 tests/language/lexer/        |  62 ++--
 tests/language/lexer/segment-test.c |  66 ++--
 tests/language/lexer/     | 134 ++++----
 15 files changed, 580 insertions(+), 476 deletions(-)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]