You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have a crash. In my case, running LC_ALL=C VDPAU_DRIVER=va_gl vdpauinfo is sufficient. (bug report)
Analyze the crash using abrt/libreport (used GNOME's abrt gui)
Have a look into the output
What happens:
unexpected message: "Reporting is disabled because the generated backtrace has low informational value.".
In my opinion, this is not true. The backtrace has some valuable info, though not in its 4 most inner frames.
To my little understanding, it is neither missing debuginfo nor the coredump is corrupted. The function has just 2 variables, temp and info. I think the backtrace is perfectly fine.
Do you still have the problem directory on hand? If so, could you please test if the retrace goes through now? We fixed a bug recently which might have caused this, so it might be worth a try.
Steps to reproduce:
LC_ALL=C VDPAU_DRIVER=va_gl vdpauinfo
is sufficient. (bug report)What happens:
unexpected message: "Reporting is disabled because the generated backtrace has low informational value.".
In my opinion, this is not true. The backtrace has some valuable info, though not in its 4 most inner frames.
What should happen:
Report the error.
Additional info:
backtrace.txt
Version info:
abrt-2.14.4-7.fc33.x86_64
libreport-2.14.0-13.fc33.x86_64
gdb-9.2-8.fc33.x86_64
vdpauinfo-1.0-16.fc33.x86_64
The text was updated successfully, but these errors were encountered: