29d58b734d
Using the talloc leak report we see that there are some msgb's that are allocated for SMS but we don't have transactions or SMS around. We need to improve the name of the messages to uniquely dscribe where they are from but the obvious leak does occur in this routine. The no available transaction id is most likely the case where we leak memory. This should not occur and shows another issue with the smsqueue/smpp handling. It doesn't explain the subscr reference count issue either. Extract of the leak report: GSM 04.11 contains 1160 bytes in 1 blocks (ref 0) 0x2517dc0 GSM 04.11 contains 1160 bytes in 1 blocks (ref 0) 0x24b56e0 GSM 04.11 contains 1160 bytes in 1 blocks (ref 0) 0x23e7930 |
||
---|---|---|
.. | ||
contrib | ||
doc | ||
include | ||
src | ||
tests | ||
tools | ||
.gitignore | ||
AUTHORS | ||
COPYING | ||
Makefile.am | ||
README | ||
configure.ac | ||
git-version-gen | ||
openbsc.pc.in | ||
osmoappdesc.py |
README
About OpenBSC ============= OpenBSC is a minimalistic implementation of the GSM Network, with particular emphasis on the functionality typically provided by the BSC, MSC, HLR, VLR and SMSC. Its currently supported interfaces towards the BTS are: * Classic A-bis over E1 using a mISDN based E1 interface. In other words, you can connect existing GSM Base Transceiver Station (BTS) through E1 to OpenBSC. So far, we have only tested the Siemens BS-11 Test reports with other BTS are much appreciated! * A-bis over IP as used by the ip.access nanoBTS product family You can find the project documentation at http://openbsc.gnumonks.org/ This project is still in its early days, and there are lots of areas where it doesn't behave as per GSM spec. Harald Welte <laforge@gnumonks.org> libosmocore =========== Please note that as of March 2010, OpenBSC has a dependency to a library called "libosmocore". You can obtain that library from git://git.osmocom.org/libosmocore.git