asterisk.ru

The ability to load/unload timing interfaces is nice, but it means that when a
timer is allocated, it may come from provider A, but later
provider B becomes the 'preferred' provider. If this happens, all
timer API calls on the timer that was provided by provider A will
actually be handed to provider B, which will say WTF and return
an error

2009-07-20 23:08 +0000 [r207522-207551] Mark Michelson <mmichelson@digium.com>

* apps/app_directed_pickup.c: Initialize connected line instance
when doing a directed pickup. This helps to prevent a crash which
may occur due to our freeing garbage due to a struct being
uninitialized.

* apps/app_directed_pickup.c: Okay, that didn't fix the crash. It
didn't really do anything useful.

2009-07-22 14:35 +0000 [r208017] Mark Michelson <mmichelson@digium.com>

* apps/app_directed_pickup.c: Fix the crash in directed pickups.
For real this time. A shallow pointer copy was causing an
ast_party_connected_line structure to be freed multiple times,
thus causing a crash. (closes issue #15441) Reported by:
lmsteffan Patches: 15441.patch uploaded by mmichelson (license
60) Tested by: lmsteffan

* CHANGES, apps/app_chanspy.c: Add the 'E' option to exit ChanSpy,
once the single channel it spied upon hangs up. In addition,
there's a bit of cleanup to the arguments and documentation, in
which I discovered that the last feature added to this
application duplicated an option (oops!)

The ability to load/unload timing interfaces is nice, but it means that when a
timer is allocated, it may come from provider A, but later
provider B becomes the 'preferred' provider. If this happens, all
timer API calls on the timer that was provided by provider A will
actually be handed to provider B, which will say WTF and return
an error

kasper писал(а):Скучно у нас на форуме. Давайте пофлудим.