libosmocore.git branch user/max/asantest updated. 0.9.0-230-g36ffc0f

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-commitlog@lists.osmocom.org/.

gitosis at osmocom.org gitosis at osmocom.org
Tue Sep 20 16:43:37 UTC 2016


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 "An utility library for Open Source Mobile Communications".

The branch, user/max/asantest has been updated
  discards  3336ff4071fb4b9be3d9476b0adfb2bbb85d9a17 (commit)
  discards  922b8d51613dd1d7e233cd25f5ef225aa4de35e7 (commit)
  discards  8c67d22c8ed8be3687fd71346fbc11067cb30bdc (commit)
  discards  b129c0d846636f698e1315a8721ab6c7b3ad77bd (commit)
       via  36ffc0f2713bdd5d57e55c9635281f08f1c6d7af (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (3336ff4071fb4b9be3d9476b0adfb2bbb85d9a17)
            \
             N -- N -- N (36ffc0f2713bdd5d57e55c9635281f08f1c6d7af)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

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 -----------------------------------------------------------------
http://cgit.osmocom.org/libosmocore/commit/?id=36ffc0f2713bdd5d57e55c9635281f08f1c6d7af

commit 36ffc0f2713bdd5d57e55c9635281f08f1c6d7af
Author: Max <msuraev at sysmocom.de>
Date:   Tue Sep 20 16:33:50 2016 +0200

    Fix ASAN failure in bitrev_test
    
    Previously while testing osmo_nibble_shift_left_unal() following error
    was triggered by AddressSanitizer:
    
    ==3890== ERROR: AddressSanitizer: stack-buffer-overflow on address 0xbff5b5b6 at pc 0xb6186862 bp 0xbff5b4a8 sp 0xbff5b49c
    READ of size 1 at 0xbff5b5b6 thread T0
        #0 0xb6186861 (/home/msuraev/source/gsm/libosmocore/src/.libs/libosmocore.so.7.0.0+0xc861)
        #1 0x8049d8b (/home/msuraev/source/gsm/libosmocore/tests/bits/.libs/lt-bitrev_test+0x8049d8b)
        #2 0x804a9d1 (/home/msuraev/source/gsm/libosmocore/tests/bits/.libs/lt-bitrev_test+0x804a9d1)
        #3 0xb5fe3af2 (/lib/i386-linux-gnu/libc-2.19.so+0x19af2)
        #4 0x8048a30 (/home/msuraev/source/gsm/libosmocore/tests/bits/.libs/lt-bitrev_test+0x8048a30)
    Address 0xbff5b5b6 is located at offset 38 in frame <main> of T0's stack:
      This frame has 3 object(s):
        [32, 38) 'in2'
        [96, 104) 'out'
        [160, 168) 'in1'
    
    The reason is incorrect range in test cycle. Fix it and adjust test
    output accordingly.
    
    Change-Id: I5eb3f600290c05b4ab9ac2450a28d616e6b415fd
    Fixes: OW#1589

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

Summary of changes:
 src/bits.c                |   8 ++--
 tests/bits/bitrev_test.c  |   6 +--
 tests/bits/bitrev_test.ok | 106 ----------------------------------------------
 3 files changed, 5 insertions(+), 115 deletions(-)


hooks/post-receive
-- 
An utility library for Open Source Mobile Communications



More information about the osmocom-commitlog mailing list