Bug 1377581 - Missing console messages before the crash
Summary: Missing console messages before the crash
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-20 07:01 UTC by Milan Crha
Modified: 2017-08-08 17:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 17:29:32 UTC
Type: Bug


Attachments (Terms of Use)

Description Milan Crha 2016-09-20 07:01:53 UTC
Please see bug #1377562, the ABRT caught the crash under wl_abort, but it didn't catch the error which the function printed before aborting. That particular error message is the most important, usually.

I saw similar issues with g_logv() calls from glib2, though there was one able to read the message from the backtrace, or at least part of it. As an example see the bug #1371448, where the var_log_messages shows nothing, while the bactrace shows the error message.

Could there be done something that the crash errors (reasons) will be caught by ABRT, please? I think of some flushall()/fsync()/whatever-similar call before asking for var_log_messages, thus it'll include the most recent output. At least in case of g_logv() the usual messages are present in the log, thus this one should be able as well.

Comment 1 Fedora End Of Life 2017-07-25 23:08:53 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-08-08 17:29:32 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.