Lots of crash reports don't have usable stackstraces

Bug #1978792 reported by Pascal Nowack
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Errors
New
Undecided
Unassigned

Bug Description

Some examples to show the problem:

https://errors.ubuntu.com/problem/1eaf2582c18effe4fcba90a9a6ed3ca0d619f9be
https://errors.ubuntu.com/problem/869b6af720409d8cf231b0131d92dc47972ddb58
https://errors.ubuntu.com/problem/8521a69e665f733041ebcde46b2541e9c0838683

Basically, these crash reports don't have any stackstrace, which makes them useless.
This is especially problematic for crashes, that appear very often, making it impossible to be able to investigate the underlying issue(s).

A pattern, that I see relatively often, is that it seems to mostly affect crashes on arm devices ('aarch64'), but crashes on amd64 devices are also affected.

Revision history for this message
Pascal Nowack (pnowack) wrote :

Looking at https://errors.ubuntu.com/?release=Ubuntu%2022.04&package=gnome-remote-desktop&period=week&pkg_arch=arm64 it seems that actually _all_ crashes on arm are without stacktraces

description: updated
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It's not all crashes on ARM, I see it often with crashes from Nvidia systems too.

Seems like we give up trying to generate a stack trace if any frame is without debug symbols. If you are able to analyse such a crash locally then there is no such problem getting a usable stack trace in gdb.

Revision history for this message
Pascal Nowack (pnowack) wrote :

> If you are able to analyse such a crash locally then there is no such problem getting a usable stack trace in gdb.

The point of Ubuntu errors is to find crashes, that I am not aware of (and that I am not being able to reproduce myself).
That means, I am unable to analyze such crashes locally. In addition to that: I don't have such ARM device (RPi 4), so I rely on Ubuntu errors here.

Personally, I also don't use Ubuntu. But since g-r-d in Ubuntu 22.04 is (currently) not patched with non-upstreamed patches, that part should not be a problem.

> It's not all crashes on ARM, I see it often with crashes from Nvidia systems too.

From what I see, it literally does affect all ARM crashes: https://errors.ubuntu.com/?release=Ubuntu%2022.04&package=gnome-remote-desktop&period=month&pkg_arch=arm64
Note: This statement does not exclude other platforms, it just says "100% of all crashes on ARM are affected by this", but does not make a statement of other platforms.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers