obexd: Split up object and session in pbap.c Object and session data is separated in PBAP plugin. Reason is that when OBEX session firstly makes disconnect of service_data, which corresponds to session in pbap.c, it than closes object, which also corresponds to session in pbap.c. Memory is deallocated after PBAP session is disconnected. When OBEX driver closes the object, it is trying to dereference the deallocated memory in order to free pbap->buffer data. Here object and session are separated, while pointers are created to make one-to-one mapping. pbap_object is created in vobject_..._open functions after query to tracker submitted. Session and object are handled separately when freed.

Diffstat

1 files changed, 59 insertions(+), 35 deletions(-)