Created attachment 872784 [details] simple example I'd like to ask for an enhancement of a faf server, to provide also raw backtraces for all threads of the crash, thus one might be able to at least overview the actual application state in the crash, instead of looking on the crashing thread, which can be sometimes misleading (memory corruption bugs and such, where, of course, whole backtrace of all threads also doesn't help, but that's just a beginning). Anyway, my idea is to have a "Raw Backtrace" button at the bottom, right beside "Backtrace Diff", like at [1], which will open a backtrace in a form of gdb's "t a a bt" command result, with couple nice-to-have improvements: a) the function names will be highlighted with a red color b) the thread names will be highlighted with a cyan color c) any variable expanded values will be discarded, but actual pointer values (addresses) will be left as they are - that will make is possible to distinguish between NULL and non-NULL pointers, and will avoid exposure of string variable contents, like passwords or server addresses. See the attached simple example. [1] https://retrace.fedoraproject.org/faf/problems/1207750/
(In reply to Milan Crha from comment #0) > b) the thread names will be highlighted with a cyan color s/cyan/teal/
> c) any variable expanded values will be discarded, but actual pointer values > (addresses) will be left as they are - that will make is possible to > distinguish between NULL and non-NULL pointers, and will avoid exposure of > string variable contents, like passwords or server addresses. See the > attached simple example. We'd need to have debuginfo installed to have access to variable contents. Not requiring debuginfo allows as to collect more reports, the tradeoff is the limited amount of information we get this way. We could include pointer values for stack frames with debuginfo already available but I'm not sure if the results are worth the effort.
Right, the c) was to make sure no private data will be exposed. If the report contains only minimal debuginfo, then even better (with respect of not exposing use private information).
I just realized that http://fpaste.org contains a 'gdb' language, which provides nice colouring of a backtrace, thus maybe you can reuse it.
Upstream ticket: https://github.com/abrt/faf/issues/309
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.