Re: [reSIProcate] DUM REFER crash

["Jason Fischl" <jason@xxxxxxxxxxxxxxx>]

You need to install a handler. It should assert in this case rather
than crash. However, it is a programming error. I don't think this can
occur from events from the wire.

On 8/18/06, Matt Porter <mporter@xxxxxxxxxxxxx> wrote:
> Dialog.cxx
>
> DebugLog (<< "Making subscription from NOTIFY: " << msg);
> ClientSubscription* sub = makeClientSubscription(msg);
> mClientSubscriptions.push_back(sub);
> ClientSubscriptionHandle client = sub->getHandle();
> mDum.mInviteSessionHandler->onReferAccepted(mInviteSession->getSessionHa
> ndle(), client, msg);
> mInviteSession->mSentRefer = false;
> sub->dispatch(request);
>
>
>
> ClientSubscription.cxx
>
> void
> ClientSubscription::dispatch(const SipMessage& msg)
> {
>    ClientSubscriptionHandler* handler =
> mDum.getClientSubscriptionHandler(mEventType);
>    assert(handler);
>
>    !!! UGG
>    handler is null, I have no handlers for event=refer
>
>
> Maybe I should have a subscription handler for a NOTIFY, event=refer.
> crashing seems to be an extreme side affect, if I don't..
> At least check the pointer before calling the method.
>
>
>
>
>
>
>
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel