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.orgThis 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 463deef8c209dd7eb023ac70bf41fa9893ad35ed (commit) via 5584a14a319044f75c9d8ea74abb6dede21ea721 (commit) from 383c5635e3920091469594ee01c2b9b13b6ea408 (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=463deef8c209dd7eb023ac70bf41fa9893ad35ed commit 463deef8c209dd7eb023ac70bf41fa9893ad35ed Author: Vadim Yanitskiy <axilirator at gmail.com> Date: Sat Sep 23 19:30:07 2017 +0330 VTY: implement talloc context introspection command This change introduces a new command, which could be used to inspect the application's talloc context directly from VTY. To enable this feature, an application need to provide it's context via the 'vty_app_info' struct, and register the VTY command by calling the osmo_talloc_vty_add_cmds(). The new command is a sub-command of 'show': show talloc-context <context> <depth> [filter] Currently the following contexts may be inspected: - application - a context provided by an application; - null - all contexts, if NULL-context tracking is enabled. A report depth is defined by the next parameter, and could be: - full - full tree report, as the talloc_report_full() does; - brief - brief tree report, as the talloc_report() does; - DEPTH - user defined maximal report depth. Also, there are two optional report filters: - regexp - print only contexts, matching a regular expression; - tree - print a specific context, pointed by specified address. The command output is formatted the same way as in case of calling the talloc_report() or talloc_report_full(). Change-Id: I43fc42880b22294d83c565ae600ac65e4f38b30d http://cgit.osmocom.org/libosmocore/commit/?id=5584a14a319044f75c9d8ea74abb6dede21ea721 commit 5584a14a319044f75c9d8ea74abb6dede21ea721 Author: Vadim Yanitskiy <axilirator at gmail.com> Date: Sat Sep 23 18:12:18 2017 +0330 vty/vty.c: do not bind vty context to application's one The 'vty_app_info' struct could be used by some applications to provide its talloc context. In the future, it will facilitate the implementation of talloc context introspection via VTY. But the 'vty' talloc context, that contains lots of items (memory chunks), is being bound to an application's one, so it becomes hard to read the last. Let's do not bind the 'vty' context automatically, until some common talloc context export policy is implemented. Change-Id: I9cb6ce9f24dbae400029e2d9f9c933fbfb16248f ----------------------------------------------------------------------- Summary of changes: include/osmocom/vty/misc.h | 1 + src/vty/Makefile.am | 3 +- src/vty/talloc_ctx_vty.c | 279 +++++++++++++++++++++++++++++++++++++++++++++ src/vty/vty.c | 2 +- 4 files changed, 283 insertions(+), 2 deletions(-) create mode 100644 src/vty/talloc_ctx_vty.c hooks/post-receive -- An utility library for Open Source Mobile Communications