Bug 1472998
| Summary: | Problem with analysing of coredump | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | vladlen.lerner | ||||||||||||
| Component: | libreport | Assignee: | abrt <abrt-devel-list> | ||||||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 25 | CC: | abrt-devel-list, gbenson, jakub, jan.kratochvil, mhabrnal, michal.toman, mkutlak, mmarusak, palves, pmuldoon, sergiodj, tom, vladlen.lerner | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2017-12-12 10:21:16 UTC | Type: | Bug | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
vladlen.lerner
2017-07-19 19:39:20 UTC
Thank you for the report. It would be very useful if you would be willing to provide us with the coredump file. (In reply to Matej Marušák from comment #1) > Thank you for the report. It would be very useful if you would be willing to > provide us with the coredump file. No, I will not not provide coredump, sorry. I agree to share only report with analysis of it with other tools, if it possible. Of course with preview and private info deletion. Also I think that bug with id 1471289 ( https://bugzilla.redhat.com/show_bug.cgi?id=1471289 ) is related to current one. It is occurred, when I tried to report about this bug with id 1472998. Same story with the bug with id 1388574 ( https://bugzilla.redhat.com/show_bug.cgi?id=1388574 ). It is occurred, when I tried to report about this bug with id 1472998. (In reply to vladlen.lerner from comment #2) > (In reply to Matej Marušák from comment #1) > > Thank you for the report. It would be very useful if you would be willing to > > provide us with the coredump file. > > No, I will not not provide coredump, sorry. I agree to share only report > with analysis of it with other tools, if it possible. Of course with preview > and private info deletion. Ok, I understand that you do not want to share coredumps, no problem there. However to solve this we will need some help from you. Can you replicate this problem (I mean the one that created the coredump) and send me steps? (In reply to Matej Marušák from comment #5) > (In reply to vladlen.lerner from comment #2) > > (In reply to Matej Marušák from comment #1) > > > Thank you for the report. It would be very useful if you would be willing to > > > provide us with the coredump file. > > > > No, I will not not provide coredump, sorry. I agree to share only report > > with analysis of it with other tools, if it possible. Of course with preview > > and private info deletion. > > Ok, I understand that you do not want to share coredumps, no problem there. > However to solve this we will need some help from you. Can you replicate > this problem (I mean the one that created the coredump) and send me steps? I am trying to replicate this problem, but still without any successes. If I get any positive result, I will inform you. But I discover two reports in the bug directory that are seemed interesting, I do not now are they full or particular analysis. Here I will attach them. Created attachment 1301533 [details]
core backtrace
Created attachment 1301534 [details]
exploitable
Created attachment 1301535 [details]
crash function
Also report-gtk created this report: https://retrace.fedoraproject.org/faf/reports/1783729/ (In reply to vladlen.lerner from comment #6) > (In reply to Matej Marušák from comment #5) > > (In reply to vladlen.lerner from comment #2) > > > (In reply to Matej Marušák from comment #1) > > > > Thank you for the report. It would be very useful if you would be willing to > > > > provide us with the coredump file. > > > > > > No, I will not not provide coredump, sorry. I agree to share only report > > > with analysis of it with other tools, if it possible. Of course with preview > > > and private info deletion. > > > > Ok, I understand that you do not want to share coredumps, no problem there. > > However to solve this we will need some help from you. Can you replicate > > this problem (I mean the one that created the coredump) and send me steps? > > I am trying to replicate this problem, but still without any successes. If I > get any positive result, I will inform you. Thank you. > But I discover two reports in > the bug directory that are seemed interesting, I do not now are they full or > particular analysis. Here I will attach them. Since your first report was about gdb hanging, could you try something, please? cd into the problem directory gdb -c coredump $(cat executable) is there something about missing debuginfos? If so, can you install them? then in gdb run 'thread apply all -ascending backtrace 2048 full' does it finish successfully? Vladen, the missing debug info might be caused by missing yum/dnf repositories. Please check if you have a repository with URL like this one https://download1.rpmfusion.org/free/fedora/releases/25/Everything/x86_64/debug/ in /etc/yum.repos.d/ I also have to inform you that even if you manage to get backtrace the reporting process will fail because it will try to open a new Bugzilla bug in Red Hat Bugzilla which does not support rpm-fusion packages. Unfortunately, it is not possible to configure ABRT/libreport to report crashes to RPM Fusion Bugzilla yet. Please, follow the steps at https://rpmfusion.org/ReportingBugs and report the telegram-desktop crash to https://bugzilla.rpmfusion.org/. You can use ABRT to analyze the coredump file so you don't need to interact with gdb directly. You can also use ABRT to create a textual report (reporter-print) and attach the text report to RPM Fusion Bugzilla. (In reply to Matej Marušák from comment #11) > (In reply to vladlen.lerner from comment #6) > > (In reply to Matej Marušák from comment #5) > > > (In reply to vladlen.lerner from comment #2) > > > > (In reply to Matej Marušák from comment #1) > > > > > Thank you for the report. It would be very useful if you would be willing to > > > > > provide us with the coredump file. > > > > > > > > No, I will not not provide coredump, sorry. I agree to share only report > > > > with analysis of it with other tools, if it possible. Of course with preview > > > > and private info deletion. > > > > > > Ok, I understand that you do not want to share coredumps, no problem there. > > > However to solve this we will need some help from you. Can you replicate > > > this problem (I mean the one that created the coredump) and send me steps? > > > > I am trying to replicate this problem, but still without any successes. If I > > get any positive result, I will inform you. > Thank you. > > But I discover two reports in > > the bug directory that are seemed interesting, I do not now are they full or > > particular analysis. Here I will attach them. > > Since your first report was about gdb hanging, could you try something, > please? > cd into the problem directory > gdb -c coredump $(cat executable) > is there something about missing debuginfos? If so, can you install them? Yes, there is output: GNU gdb (GDB) Fedora 7.12.1-48.fc25 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/telegram-desktop... warning: the debug information found in "/usr/lib/debug//usr/bin/telegram-desktop.debug" does not match "/usr/bin/telegram-desktop" (CRC mismatch). Reading symbols from /usr/bin/telegram-desktop...(no debugging symbols found)...done. (no debugging symbols found)...done. warning: core file may not match specified executable file. [New LWP 1998] [New LWP 2024] [New LWP 2006] [New LWP 2013] [New LWP 2011] [New LWP 2010] [New LWP 2015] [New LWP 2014] [New LWP 2000] [New LWP 2001] [New LWP 2093] [New LWP 1999] warning: the debug information found in "/usr/lib/debug//lib64/libtgvoip.so.0.4.1.debug" does not match "/lib64/libtgvoip.so.0.4.1" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libavformat.so.57.41.100.debug" does not match "/lib64/libavformat.so.57" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libavformat.so.57.41.100.debug" does not match "/lib64/libavformat.so.57" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libavcodec.so.57.48.101.debug" does not match "/lib64/libavcodec.so.57" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libavcodec.so.57.48.101.debug" does not match "/lib64/libavcodec.so.57" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libswresample.so.2.1.100.debug" does not match "/lib64/libswresample.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libswresample.so.2.1.100.debug" does not match "/lib64/libswresample.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libswscale.so.4.1.100.debug" does not match "/lib64/libswscale.so.4" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libswscale.so.4.1.100.debug" does not match "/lib64/libswscale.so.4" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libavutil.so.55.28.100.debug" does not match "/lib64/libavutil.so.55" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libavutil.so.55.28.100.debug" does not match "/lib64/libavutil.so.55" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libpthread-2.24.so.debug" does not match "/lib64/libpthread.so.0" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libpthread-2.24.so.debug" does not match "/lib64/libpthread.so.0" (CRC mismatch). [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". warning: the debug information found in "/usr/lib/debug//lib64/libm-2.24.so.debug" does not match "/lib64/libm.so.6" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libm-2.24.so.debug" does not match "/lib64/libm.so.6" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libc-2.24.so.debug" does not match "/lib64/libc.so.6" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libc-2.24.so.debug" does not match "/lib64/libc.so.6" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/librt-2.24.so.debug" does not match "/lib64/librt.so.1" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/librt-2.24.so.debug" does not match "/lib64/librt.so.1" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libdl-2.24.so.debug" does not match "/lib64/libdl.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libdl-2.24.so.debug" does not match "/lib64/libdl.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libproxy.so.1.0.0.debug" does not match "/lib64/libproxy.so.1" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libproxy.so.1.0.0.debug" does not match "/lib64/libproxy.so.1" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libsystemd.so.0.16.0.debug" does not match "/lib64/libsystemd.so.0" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libsystemd.so.0.16.0.debug" does not match "/lib64/libsystemd.so.0" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/ld-2.24.so.debug" does not match "/lib64/ld-linux-x86-64.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/ld-2.24.so.debug" does not match "/lib64/ld-linux-x86-64.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libresolv-2.24.so.debug" does not match "/lib64/libresolv.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libresolv-2.24.so.debug" does not match "/lib64/libresolv.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libnss_files-2.24.so.debug" does not match "/lib64/libnss_files.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libnss_files-2.24.so.debug" does not match "/lib64/libnss_files.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libinput.so.10.11.5.debug" does not match "/lib64/libinput.so.10" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libinput.so.10.11.5.debug" does not match "/lib64/libinput.so.10" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libudev.so.1.6.5.debug" does not match "/lib64/libudev.so.1" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libudev.so.1.6.5.debug" does not match "/lib64/libudev.so.1" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libutil-2.24.so.debug" does not match "/lib64/libutil.so.1" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libutil-2.24.so.debug" does not match "/lib64/libutil.so.1" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libnsl-2.24.so.debug" does not match "/lib64/libnsl.so.1" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libnsl-2.24.so.debug" does not match "/lib64/libnsl.so.1" (CRC mismatch). Core was generated by `/usr/bin/telegram-desktop --'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007fb12fd4a717 in gdk_pixbuf_get_from_surface () from /lib64/libgdk-3.so.0 [Current thread is 1 (Thread 0x7fb14c054940 (LWP 1998))] Missing separate debuginfos, use: dnf debuginfo-install telegram-desktop-1.1.7-1.fc25.x86_64 I executed 'dnf debuginfo-install telegram-desktop-1.1.7-1.fc25.x86_64', it is installed successfully. But after when I tried to execute 'gdb -c coredump $(cat executable)' it still return same output. > then in gdb run 'thread apply all -ascending backtrace 2048 full' does it > finish successfully? Despite my previous answer I tried to execute 'thread apply all -ascending backtrace 2048 full'. I will attach log of it's output Created attachment 1301663 [details]
gdb apply all log file
output of executing in gdb 'thread apply all -ascending backtrace 2048 full'
(In reply to Jakub Filak from comment #12) > Vladen, the missing debug info might be caused by missing yum/dnf > repositories. Please check if you have a repository with URL like this one > https://download1.rpmfusion.org/free/fedora/releases/25/Everything/x86_64/ > debug/ in /etc/yum.repos.d/ > > I also have to inform you that even if you manage to get backtrace the > reporting process will fail because it will try to open a new Bugzilla bug > in Red Hat Bugzilla which does not support rpm-fusion packages. > > Unfortunately, it is not possible to configure ABRT/libreport to report > crashes to RPM Fusion Bugzilla yet. > > Please, follow the steps at https://rpmfusion.org/ReportingBugs and report > the telegram-desktop crash to https://bugzilla.rpmfusion.org/. > > You can use ABRT to analyze the coredump file so you don't need to interact > with gdb directly. You can also use ABRT to create a textual report > (reporter-print) and attach the text report to RPM Fusion Bugzilla. If it will be necessary, I will do that. Thank you. This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. |