- 22 5月, 2013 16 次提交
-
-
由 Michael S Collins 提交于
-
由 William King 提交于
-
由 Anthony Minessale 提交于
FS-5402 --resolve the problem is ent originate has many channels and many causes to parse so we need to check it against all the causes
-
由 Anthony Minessale 提交于
-
-
由 Chris Rienzo 提交于
-
由 Anthony Minessale 提交于
-
由 Jeff Lenk 提交于
-
由 Nathan Neulinger 提交于
-
由 Nathan Neulinger 提交于
FS-5379: --resolve fix skinny phone codec agreement issues due to incorrect hardwired ptime, update field names for future coding to be more descriptive
-
由 Nathan Neulinger 提交于
-
由 Nathan Neulinger 提交于
-
由 Chris Rienzo 提交于
-
由 Chris Rienzo 提交于
-
由 Chris Rienzo 提交于
-
由 Anthony Minessale 提交于
-
- 21 5月, 2013 11 次提交
-
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
由 Stefan Knoblich 提交于
Catch single channel RESTART/RESTART ACK events for non-B-channels, that would lead to a NULL pointer dereference, because those do not have per-channel private data (chan->call_data = chan_priv == NULL). Signed-off-by:
Stefan Knoblich <stkn@openisdn.net>
-
由 Chris Rienzo 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
- 20 5月, 2013 6 次提交
-
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
由 Chris Rienzo 提交于
-
由 Chris Rienzo 提交于
-
由 Steve Underwood 提交于
FS5202.
-
- 19 5月, 2013 7 次提交
-
-
由 William King 提交于
-
由 William King 提交于
Theoretical memory leak where if attr_init failed, then check would have still been malloc'd but not used.
-
由 William King 提交于
Minor code cleanup. calling va_start without calling va_end doesn't leak does it? Either way, it's fixed now.
-
由 William King 提交于
full_contact must be freed by sofia. There isn't a chance of this having blown anything up, but Coverity is right that this should be initialized with NULL to be safe against future refactors.
-
由 William King 提交于
Was causing a very small leak on naptr lookups. Upon review just happened to be a typo missing a bang.
-
由 William King 提交于
My bad. some how a make didn't catch this issue after a cleanup refactor. In this instance buf is being treated as an 8 byte number, not a pointer.
-
由 William King 提交于
Coverity reported an Uninitialized pointer read. Upon further digging it appears that there is a code path where incoming packets can come in out of order, so this section of code tries to see if it can find the missed packets. As per FS-5202 there is a case where under heavy load the packet exists, and has most of the packet parsed, but still has a NULL pointer for the packet buffer. These two lines would at least help detect the edge case.
-