[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: Is there (going to be) an auto-retracer service for KDE?
From: Elv1313 <elv1313 () gmail ! com>
Date: 2021-04-28 7:35:24
Message-ID: CAFnK6VVkaJREvxXGg1kcu6Dgf2TjiEXE9gyV+ppCSA5T0jjTqg () mail ! gmail ! com
[Download RAW message or body]
> Automatic symbolication services are great, but they need to be run by
> distros, because distros are the ones who build their own binaries.
Until recently that was mostly true, but now that half of the major distros
ships with `debuginfod`, there is such a service.
https://lwn.net/Articles/847256/
https://lwn.net/Articles/852416/
These days I don't have the bandwidth to code in KDE much, but if someone
has time, I think there is a path forward here.
Assuming `debuginfod` works, it would be possible to implement a button
that
sends the backtrace, full backtrace or full core dump to bugs.kde.org. Of
course, that should be an explicit button like in Firefox or Windows
98/Me/2x/XP, not something done silently in the background like
"some other products".
Having worked a lot of the Apport data back in the day where I maintained
sflphone-kde, this data is super useful. As a network face app, most bugs
were obscure network race contitions in low level libraries like pjsip,
GNU telephony and ffmpeg. The odds of ever getting those in regular
integration tests was literally zero. So the aport data was invaluable.
On Sun, 25 Apr 2021 at 17:19, Nate Graham <nate@kde.org> wrote:
> Hello Lyubomir,
>
> Automatic symbolication services are great, but they need to be run by
> distros, because distros are the ones who build their own binaries.
>
> The problem with apport is that it reports bugs to Ubuntu, not to us.
> Some of these bug reports get forwarded to us, but most don't. As a
> result they mostly don't help us. Our own crash reporting tool is
> generic and cross-distro, but as a consequence, it isn't hooked into
> distro-specific remote symbolication services. It does however have
> facilities to automatically fetch symbols when needed. Sometimes this
> doesn't work as well as it should, but the feature is there.
>
> Nate
>
>
> On 4/25/21 3:55 PM, Lyubomir Parvanov wrote:
> > I'm not much into KDE bug reporting and also not much into Apport. I'm
> > simply a user.
> >
> > However, what i know is that as a previous Gnome user i never saw a
> > "Gnome reporter" piece of software. As a KDE user now I frequently see
> > the specific "KDE bug reporter" piece of software, and it never ever
> > reported a crash because it misses symbols. I know that Linux users are
> > supposed to know their way around the terminal, but still...
> >
> > Also I know that as KDE developers you can register at
> > https://errors.ubuntu.com/ <https://errors.ubuntu.com/> via the form.
> > I also know about THIS <https://youtu.be/PPQ7k0jRUE4?t=1781> video
> which
> > although it is old is still relevant.
> >
> > KDE doesn't run only on Ubuntu and Apport might be an Ubuntu software,
> > but surely it can be configured by default to be used on Ubuntu, can't
> it?
> >
> > This thread was meant as a question and/or discussion, mainly fuelled by
> > my thoughts and experiences with Apport which seems to be a more
> > convenient way of error collection.
>
[Attachment #3 (text/html)]
<div dir="ltr"><span style="font-family:monospace"><span \
style="color:rgb(0,0,0);background-color:rgb(255,255,255)">> Automatic \
symbolication services are great, but they need to be run by </span><br>> distros, \
because distros are the ones who build their own binaries. <br>
<br>Until recently that was mostly true, but now that half of the major distros
<br>ships with `debuginfod`, there is such a service.
<br>
<br><a href="https://lwn.net/Articles/847256/">https://lwn.net/Articles/847256/</a>
<br><a href="https://lwn.net/Articles/852416/">https://lwn.net/Articles/852416/</a>
<br>
<br>These days I don't have the bandwidth to code in KDE much, but if someone
<br>has time, I think there is a path forward here.
<br>
<br>Assuming `debuginfod` works, it would be possible to implement a button that
<br>sends the backtrace, full backtrace or full core dump to <a \
href="http://bugs.kde.org">bugs.kde.org</a>. Of <br>course, that should be an \
explicit button like in Firefox or Windows <br>98/Me/2x/XP, not something done \
silently in the background like <br>"some other products".
<br>
<br>Having worked a lot of the Apport data back in the day where I maintained
<br>sflphone-kde, this data is super useful. As a network face app, most bugs
<br>were obscure network race contitions in low level libraries like pjsip, \
<br>GNU telephony and ffmpeg. The odds of ever getting those in regular \
<br>integration tests was literally zero. So the aport data was invaluable.<br> \
<br><br></span></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Sun, 25 Apr 2021 at 17:19, Nate Graham <<a \
href="mailto:nate@kde.org">nate@kde.org</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">Hello Lyubomir,<br> <br>
Automatic symbolication services are great, but they need to be run by <br>
distros, because distros are the ones who build their own binaries.<br>
<br>
The problem with apport is that it reports bugs to Ubuntu, not to us. <br>
Some of these bug reports get forwarded to us, but most don't. As a <br>
result they mostly don't help us. Our own crash reporting tool is <br>
generic and cross-distro, but as a consequence, it isn't hooked into <br>
distro-specific remote symbolication services. It does however have <br>
facilities to automatically fetch symbols when needed. Sometimes this <br>
doesn't work as well as it should, but the feature is there.<br>
<br>
Nate<br>
<br>
<br>
On 4/25/21 3:55 PM, Lyubomir Parvanov wrote:<br>
> I'm not much into KDE bug reporting and also not much into Apport. I'm \
<br> > simply a user.<br>
> <br>
> However, what i know is that as a previous Gnome user i never saw a <br>
> "Gnome reporter" piece of software. As a KDE user now I frequently see \
<br> > the specific "KDE bug reporter" piece of software, and it never \
ever <br> > reported a crash because it misses symbols. I know that Linux users \
are <br> > supposed to know their way around the terminal, but still...<br>
> <br>
> Also I know that as KDE developers you can register at <br>
> <a href="https://errors.ubuntu.com/" rel="noreferrer" \
target="_blank">https://errors.ubuntu.com/</a> <<a \
href="https://errors.ubuntu.com/" rel="noreferrer" \
target="_blank">https://errors.ubuntu.com/</a>> via the form.<br> > I also know \
about THIS <<a href="https://youtu.be/PPQ7k0jRUE4?t=1781" rel="noreferrer" \
target="_blank">https://youtu.be/PPQ7k0jRUE4?t=1781</a>> video which <br> > \
although it is old is still relevant.<br> > <br>
> KDE doesn't run only on Ubuntu and Apport might be an Ubuntu software, <br>
> but surely it can be configured by default to be used on Ubuntu, can't \
it?<br> > <br>
> This thread was meant as a question and/or discussion, mainly fuelled by <br>
> my thoughts and experiences with Apport which seems to be a more <br>
> convenient way of error collection.<br>
</blockquote></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic