- 25 5月, 2013 7 次提交
-
-
由 William King 提交于
-
由 William King 提交于
-
由 William King 提交于
More explicit and defensive code so if the init fails we know we handling this pointer safely, because rc_config_init will free the pointer if there was a problem, but it will not set the pointer to NULL.
-
由 William King 提交于
-
由 William King 提交于
-
由 William King 提交于
Appears to have been a copy paste error because this doesn't do what the api claims, and it also leaks the reference to the new node.
-
由 William King 提交于
-
- 24 5月, 2013 8 次提交
-
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
由 Mariusz Czułada 提交于
-
由 Raymond Chandler 提交于
-
由 Jeff Lenk 提交于
-
由 Jeff Lenk 提交于
-
由 Raymond Chandler 提交于
-
由 Anthony Minessale 提交于
-
- 23 5月, 2013 4 次提交
-
-
由 Anthony Minessale 提交于
FS-5453 --resolve this is a different issue, we just have to hangup the loopback channel so the loopback and the sip don't both execute the extension
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
- 22 5月, 2013 3 次提交
-
-
由 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 提交于
-
由 Anthony Minessale 提交于
-
- 21 5月, 2013 7 次提交
-
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
- 20 5月, 2013 3 次提交
-
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
由 Ken Rice 提交于
-
- 19 5月, 2013 8 次提交
-
-
由 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 提交于
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.
-
由 William King 提交于
Edge case for when you are subscribing to presence on a valet parking lot. In which case there would be a small leak.
-
由 William King 提交于
Possible leak if someone were to try and add extra headers to a channel that had either an inbound info on that session or the session were to be deflected. I don't see a way that these extra headers could be added outside of a C module subscribing to the session states, but just to make sure I'm adding these so that just like other extra header locations it's cleaned up.
-