sharkcz (sharkcz) wrote,
sharkcz
sharkcz

Why it's useful to use a deskop on ppc64le

I want provide a short example what I've met in the past weeks when dog-fooding a ppc64le Fedora desktop environment on my OpenPOWER based Talos II. We have experienced segfaults coming from a smashed stack in some desktop components, although no one using the mainstream arches noticed them. The toolchain guys will be able to explain why eg. x86_64 is immune (or just lucky), but the problems were real issues in the projects' source code. The common denominator was an incorrect callback signature for GTK+ based apps, the callbacks expected different parameters than were passed by their callers. And this kind of inconsistency can't be found during compile time. IMHO it opens possibilities for some static analysis before producing the binaries by looking at the signal definitions in GTK+ and what functions/callbacks are then attached to them in the projects. Or for some AI that will analyze the crashes and look for the common pattern and recommend a solution. And what's the conclusion - as usually, heterogenity helps to improve quality :-)

Now the details:

  • gcr-promter - this annoyed me a lot, every time I used "ssh" :-)
    https://bugzilla.redhat.com/show_bug.cgi?id=1631759
    https://gitlab.gnome.org/GNOME/gcr/merge_requests/16

  • LibreOffice Draw - kudos to Caolán for the prompt fix
    https://bugzilla.redhat.com/show_bug.cgi?id=1719378
    https://gerrit.libreoffice.org/#/c/73829/

  • gthumb
    https://bugzilla.redhat.com/show_bug.cgi?id=1720701
    https://gitlab.gnome.org/GNOME/gthumb/merge_requests/6
  • Subscribe

    • Post a new comment

      Error

      Anonymous comments are disabled in this journal

      default userpic

      Your IP address will be recorded 

    • 0 comments