vty talloc report

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/OpenBSC@lists.osmocom.org/.

Vadim Yanitskiy axilirator at gmail.com
Thu Jun 1 07:48:17 UTC 2017


Great news,

> Of course, we can write a new function and register every
> root talloc context using it. What about that?

I just found, that talloc context may be specified in vty_app_info
structure:

/*! Information an application registers with the VTY */
struct vty_app_info {
    /*! \brief name of the application */
    const char *name;
    /*! \brief version string of the application */
    const char *version;
    /*! \brief copyright string of the application */
    const char *copyright;
    /*! \brief \ref talloc context */
    void *tall_ctx;
    // ...
}

But almost all osmo* applications don't set this pointer.

With best regards,
Vadim Yanitskiy.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170601/d3e7c7b8/attachment.htm>


More information about the OpenBSC mailing list