Bug 1472998 - Problem with analysing of coredump
Problem with analysing of coredump
Status: NEW
Product: Fedora
Classification: Fedora
Component: libreport (Show other bugs)
25
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: abrt
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-19 15:39 EDT by vladlen.lerner
Modified: 2017-07-20 07:00 EDT (History)
14 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
backtrace of gdb analysis (19.41 KB, text/plain)
2017-07-19 15:39 EDT, vladlen.lerner
no flags Details
core backtrace (9.31 KB, text/plain)
2017-07-20 03:12 EDT, vladlen.lerner
no flags Details
exploitable (82 bytes, text/plain)
2017-07-20 03:13 EDT, vladlen.lerner
no flags Details
crash function (13 bytes, text/plain)
2017-07-20 03:14 EDT, vladlen.lerner
no flags Details
gdb apply all log file (37.07 KB, text/plain)
2017-07-20 06:56 EDT, vladlen.lerner
no flags Details

  None (edit)
Description vladlen.lerner 2017-07-19 15:39:20 EDT
Created attachment 1301304 [details]
backtrace of gdb analysis

Hello, I have some problem with bug reporting using report-gtk, in particular, in my opinion, with coredump analyses (according to backtrace of analyses) 

Description of problem:

One day I tried to move pointer to between two contacts in my contact list in telegram-desktop application (from rpm-fusion repo). And application suddenly stuck and then - closed with the notification of bug from report-gtk.
When I try to report about this bug with report gtk and refuse to upload my coredump, but agree to download some tools for local analysis I see the message:

"
--- Running report_uReport ---
('report_uReport' completed successfully)

--- Running analyze_CCpp ---
Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'NO'
Analyzing coredump 'coredump'
Coredump references 218 debuginfo files, 4 of them are not installed
Initializing package manager
Setting up repositories
Looking for needed packages in repositories
Can't find packages for 4 debuginfo files
Removing /var/tmp/abrt-tmp-debuginfo.FbUHKZ
Missing debuginfo file: /usr/lib/debug/.build-id/f9/7055a5f056919b8b91f741d61141916cce1cfc.debug
Missing debuginfo file: /usr/lib/debug/.build-id/0b/0c7442fb48cdc801d435214a5a2d44b81cddd8.debug
Missing debuginfo file: /usr/lib/debug/.build-id/47/48f888bec2f6d397ff91036bae045fc713241f.debug
Missing debuginfo file: /usr/lib/debug/.build-id/2c/fe64d9497150c5214dde418cc4d1813312bb04.debug
Generating backtrace
Backtrace is generated and saved, 19874 bytes
Looking for similar problems in bugzilla
"




When I open manually backtrace of this analysis, I discover log, which ended such way:
"Looks like gdb hung while generating backtrace.
This may be a bug in gdb. Consider submitting a bug report to gdb developers.
Please attach coredump from this crash to the bug report if you do."




Also I tried to use report-cli and it recommended me to use command 'debuginfo-install telegram-desktop-1.1.7-1.fc25'. I followed this advice but using report-gtk and report-cli still not successful.
Also I use this guide: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Developer_Guide/intro.debuginfo.html and try to found missing packages manually with the command like this:

repoquery --disablerepo='*' --enablerepo='*-debug*' -qf "path2missing_file"

but it was not successful too.

Version-Release number of selected component (if applicable):
GNU gdb (GDB) Fedora 7.12.1-48.fc25



How can I fix the problem to report about the bug with telegram-desktop with report-gtk?
Comment 1 Matej Marušák 2017-07-19 16:40:41 EDT
Thank you for the report. It would be very useful if you would be willing to provide us with the coredump file.
Comment 2 vladlen.lerner 2017-07-19 17:31:59 EDT
(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.
Comment 3 vladlen.lerner 2017-07-19 17:38:36 EDT
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.
Comment 4 vladlen.lerner 2017-07-19 17:47:41 EDT
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.
Comment 5 Matej Marušák 2017-07-20 01:06:38 EDT
(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?
Comment 6 vladlen.lerner 2017-07-20 03:05:33 EDT
(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.
Comment 7 vladlen.lerner 2017-07-20 03:12 EDT
Created attachment 1301533 [details]
core backtrace
Comment 8 vladlen.lerner 2017-07-20 03:13 EDT
Created attachment 1301534 [details]
exploitable
Comment 9 vladlen.lerner 2017-07-20 03:14 EDT
Created attachment 1301535 [details]
crash function
Comment 10 vladlen.lerner 2017-07-20 03:19:46 EDT
Also report-gtk created this report: https://retrace.fedoraproject.org/faf/reports/1783729/
Comment 11 Matej Marušák 2017-07-20 04:30:32 EDT
(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?
Comment 12 Jakub Filak 2017-07-20 04:53:40 EDT
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.
Comment 13 vladlen.lerner 2017-07-20 06:54:57 EDT
(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
Comment 14 vladlen.lerner 2017-07-20 06:56 EDT
Created attachment 1301663 [details]
gdb apply all log file

output of executing in gdb 'thread apply all -ascending backtrace 2048 full'
Comment 15 vladlen.lerner 2017-07-20 07:00:16 EDT
(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.

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