Don't use KCrash on Android
AbandonedPublic

Authored by nicolasfella on Sep 17 2019, 2:40 PM.

Details

Reviewers
dfaure
Summary

We don't want/have KCrash on Android, so diable the pieces there

Test Plan

builds on Linux and Android

Diff Detail

Repository
R241 KIO
Branch
nokcrash
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 16681
Build 16699: arc lint + arc unit
nicolasfella created this revision.Sep 17 2019, 2:40 PM
Restricted Application added a project: Frameworks. · View Herald TranscriptSep 17 2019, 2:40 PM
Restricted Application added a subscriber: kde-frameworks-devel. · View Herald Transcript
nicolasfella requested review of this revision.Sep 17 2019, 2:40 PM

Can't we make KCrash just no-op on Android?

Can't we make KCrash just no-op on Android?

It pretty much is. The problem I'm fixing only started to arise when I blacklisted it on the Android builds because it's 1) useless 2) brings in KWindowSytem as a dependency.

It pretty much boils down to the general question of whether we prefer having no-op/dummy stuff or explicitely exclude them on Android

apol added a subscriber: apol.Sep 17 2019, 2:51 PM

Why not? it could be useful. The alternative is darkness over what happened there.

I surely don't want to have apps start to #ifdef a ton of stuff out, which works against the nature of Frameworks.

I think the line between dummy and #ifdef is in the commit message: if we don't want something on Android #ifdef is IMHO the way to go, if we merely don't have something yet, let's go for the dummy. A crash handler/bug reporter is something we certainly want I'd say, but something that currently isn't working yet.

apol added a comment.Sep 17 2019, 5:56 PM

I think the line between dummy and #ifdef is in the commit message: if we don't want something on Android #ifdef is IMHO the way to go, if we merely don't have something yet, let's go for the dummy. A crash handler/bug reporter is something we certainly want I'd say, but something that currently isn't working yet.

if we start ifdef'ing it out now, the day it works, we'll have to ifdef it back.
Also I don't really see why it shouldn't work at all now, is all the API missing? (haven't looked at it yet)

In D24025#533428, @apol wrote:

I think the line between dummy and #ifdef is in the commit message: if we don't want something on Android #ifdef is IMHO the way to go, if we merely don't have something yet, let's go for the dummy. A crash handler/bug reporter is something we certainly want I'd say, but something that currently isn't working yet.

if we start ifdef'ing it out now, the day it works, we'll have to ifdef it back.

That was exactly my point, let's not ifdef stuff we want eventually, like a crash handler, ifdef is for things that conceptually don't exist IMHO, like kauth/kdesu due to lack of a concept of elevated privileges. Sorry for confusing wording :)

Also I don't really see why it shouldn't work at all now, is all the API missing? (haven't looked at it yet)

AFAIK KCrash depends on gdb to produce useful results, no?

dfaure requested changes to this revision.Apr 14 2020, 9:07 PM

see Volker's comment

This revision now requires changes to proceed.Apr 14 2020, 9:07 PM
nicolasfella abandoned this revision.May 18 2020, 4:01 PM