From f3c2f6665f2102f7bfac9374712444271e383668 Mon Sep 17 00:00:00 2001 From: Dario Casalinuovo Date: Mon, 14 Nov 2016 19:09:48 +0100 Subject: [PATCH] MediaRoster: Don't allow rosters without a BApplication * The BeBook states that any media_kit app should have BApplication behind. Beware the app don't need to be running, but the object should be present. This is because we use BApplication as a safe exit point to free the memory allocated. * While I was a bit reclutant in doing that, after a developer discussion we agreed this would be the cleaner way to solve this problem without eluding it. --- src/kits/media/MediaRoster.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/kits/media/MediaRoster.cpp b/src/kits/media/MediaRoster.cpp index c928736a7a..15c5fb30e2 100644 --- a/src/kits/media/MediaRoster.cpp +++ b/src/kits/media/MediaRoster.cpp @@ -2302,7 +2302,7 @@ BMediaRoster::Roster(status_t* out_error) BAutolock lock(sInitLocker); if (be_app == NULL) - TRACE("Warning! You should have a valid BApplication."); + debugger("Warning! You should have a valid BApplication."); if (!lock.IsLocked()) return NULL;