libosmocore.git branch master updated. 0.9.0-310-ga65e993

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
Fri Dec 9 17:06:55 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, master has been updated
       via  a65e99331a9699a09d2661b595c1723eea51873f (commit)
       via  a24be85dc41885ee77072af9f079c69c575061e9 (commit)
      from  665d48bf15602e8666b292dbe66881786af2ea95 (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 -----------------------------------------------------------------
http://cgit.osmocom.org/libosmocore/commit/?id=a65e99331a9699a09d2661b595c1723eea51873f

commit a65e99331a9699a09d2661b595c1723eea51873f
Author: Harald Welte <laforge at gnumonks.org>
Date:   Fri Dec 2 13:54:36 2016 +0100

    gsmtap: Add defintions for GSMTAP based remote logging
    
    Often it is useful to have log statements from the osmocom programs
    synchronized with protocol traces.  So rather than having to open the
    pcap file with GSMTAP or other protocol data side-by-side with the
    textual log of one or more network elements, we simply pass the log
    lines around as GSMTAP messages, which can then be displayed in-order
    and interspersed with the protocol messages inside wireshark.
    
    Change-Id: I33ab530e10ef0311b6f80b731e61894f20b4b3e7

http://cgit.osmocom.org/libosmocore/commit/?id=a24be85dc41885ee77072af9f079c69c575061e9

commit a24be85dc41885ee77072af9f079c69c575061e9
Author: Harald Welte <laforge at gnumonks.org>
Date:   Fri Dec 9 17:58:17 2016 +0100

    Fix msgb_test on 64 bit architectures
    
    truncating the unsigned long pointer msg->data to 'int' and then passin
    git into msgb_resize_area() is unsafe as depending on the 32rd address
    bit it will be eiether negative or positive.  That will in turn change
    the expected "Sub area is not fully contained in the msg data\n" error
    message into "Negative sizes are not allowed\n" which is not what the
    autotest case expects.
    
    Change-Id: I87ce13c265704d4ba8724e7dc7ed874c1128e0fa

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

Summary of changes:
 include/osmocom/core/gsmtap.h | 19 +++++++++++++++++++
 tests/msgb/msgb_test.c        |  2 +-
 2 files changed, 20 insertions(+), 1 deletion(-)


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



More information about the osmocom-commitlog mailing list