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/.
Pablo Neira Ayuso pablo at gnumonks.orgOn Fri, Sep 16, 2011 at 01:20:56AM +0200, Holger Hans Peter Freyther wrote: > On 09/16/2011 01:12 AM, Pablo Neira Ayuso wrote: > > On Thu, Sep 15, 2011 at 12:56:56PM +0200, Daniel Willmann wrote: > > > > > Thanks for the patches, nice catch the leak fix. > > This fix reminded me that we should have some way to test for 'leaks', semi > automatically. What I have done so far with On-Waves when deploying/branching > was to have a setup with two phones (Motorola A1200, Nokia ...), some crazy > chat script to call ATD, AT, send SMS from the Motorola phone, have another > script that 'scripts' telnet to either drop OML/RSL and on top of that have > another script that is using tcpkill, sending SIGKILL2 to drop the MSC > connection... > > Leak checking was done by using the talloc reporting (it also shows that not > every context hangs of the right roots), using top -p `pidof ...`. It would be > nice if we could automate this and extend it to the various external > interfaces (e.g. CTRL). I see, automating leak checking seems hard to achieve. In other tools that I have, I added some command to display something similar to the talloc reporting so I could use it to check if my program was leaking at some pool (and if so, reviewing the code that allocates memory in that pool). Probably we can add that command to display the talloc report to the generic VTY interface in libosmocore.