Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unexpected message: "Reporting is disabled because the generated backtrace has low informational value." #683

Open
genodeftest opened this issue Nov 7, 2020 · 3 comments
Labels

Comments

@genodeftest
Copy link
Contributor

genodeftest commented Nov 7, 2020

Steps to reproduce:

  1. Have a crash. In my case, running LC_ALL=C VDPAU_DRIVER=va_gl vdpauinfo is sufficient. (bug report)
  2. Analyze the crash using abrt/libreport (used GNOME's abrt gui)
  3. 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.

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

@mgrabovsky mgrabovsky added this to Needs triage in Issue review via automation Nov 7, 2020
@mgrabovsky mgrabovsky added the bug label Nov 7, 2020
@xsuchy
Copy link
Member

xsuchy commented Nov 10, 2020

What you have in details of that message? Options are either:

  1. Please try to install debuginfo manually using the command:... or
  2. A proper debuginfo is probably missing or the coredump is corrupted

@genodeftest
Copy link
Contributor Author

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.

@mgrabovsky
Copy link
Contributor

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.

@xsuchy xsuchy moved this from Needs triage to Someday in future, maybe in Issue review Dec 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Issue review
  
Someday in future, maybe
Development

No branches or pull requests

3 participants