On 07/11/2025 11:50, Zbigniew Jędrzejewski-Szmek wrote:
That's not quite true. For many types of C code bugs, having a report that says "look, it crashes_here_ trying to dereference NULL" is enough.
I had many bug reports filed against my packages in the RHBZ bug tracking system, with the failures being caused by internal components of Glib/Qt, etc.
I think abrt should track this and not create bug reports if the crash didn't occur in a package module.
Having additional context and repro instructions is of course useful, but even without that bug reports have value.
I think the abrt needs to be modified so that it uses the standard Fedora bug report template (of course, some fields, such as the operating system version/architecture, can be filled in automatically), including steps how to reproduce the crash.
-- Sincerely, Vitaly Zaitsev ([email protected]) -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
