Bug 1400661 - reporting disabled because the backtrace is unusable
Summary: reporting disabled because the backtrace is unusable
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 25
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-12-01 18:12 UTC by Mikhail
Modified: 2017-12-12 10:04 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:04:42 UTC
Type: Bug


Attachments (Terms of Use)
ccpp-2016-12-01-22:16:23-4049 (5.01 MB, application/x-xz)
2016-12-01 18:12 UTC, Mikhail
no flags Details

Description Mikhail 2016-12-01 18:12:35 UTC
Created attachment 1226964 [details]
ccpp-2016-12-01-22:16:23-4049

Description of problem:
reporting disabled because the backtrace is unusable, why? I manually install all debug symbols.

(gdb) thread apply all bt

Thread 15 (Thread 0x7fffd0b40700 (LWP 9771)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x00007ffff2c0ca7a in g_cond_wait_until (cond=cond@entry=0x555555908a68, mutex=mutex@entry=0x555555908a60, end_time=end_time@entry=84206442383) at gthread-posix.c:1442
#2  0x00007ffff2b9b8c9 in g_async_queue_pop_intern_unlocked (queue=queue@entry=0x555555908a60, wait=wait@entry=1, end_time=end_time@entry=84206442383) at gasyncqueue.c:422
#3  0x00007ffff2b9beec in g_async_queue_timeout_pop (queue=0x555555908a60, timeout=timeout@entry=15000000) at gasyncqueue.c:543
#4  0x00007ffff2bef5cd in g_thread_pool_wait_for_new_pool () at gthreadpool.c:167
#5  g_thread_pool_thread_proxy (data=<optimized out>) at gthreadpool.c:364
#6  0x00007ffff2beeb03 in g_thread_proxy (data=0x7fffb1e9cf20) at gthread.c:784
#7  0x00007ffff25ff6ca in start_thread (arg=0x7fffd0b40700) at pthread_create.c:333
#8  0x00007ffff2339f6f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7fffd18d0700 (LWP 9714)):
#0  0x00007ffff232e00d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007ffff2bc7156 in g_main_context_poll (priority=<optimized out>, n_fds=1, fds=0x7fffc80010c0, timeout=<optimized out>, context=0x555555926310) at gmain.c:4228
#2  g_main_context_iterate (context=context@entry=0x555555926310, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3924
#3  0x00007ffff2bc726c in g_main_context_iteration (context=context@entry=0x555555926310, may_block=may_block@entry=1) at gmain.c:3990
#4  0x00007fffd18d7fad in dconf_gdbus_worker_thread (user_data=0x555555926310) at dconf-gdbus-thread.c:82
#5  0x00007ffff2beeb03 in g_thread_proxy (data=0x5555558f74f0) at gthread.c:784
#6  0x00007ffff25ff6ca in start_thread (arg=0x7fffd18d0700) at pthread_create.c:333
#7  0x00007ffff2339f6f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7fffd22de700 (LWP 9713)):
#0  0x00007ffff232e00d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007ffff2bc7156 in g_main_context_poll (priority=<optimized out>, n_fds=6, fds=0x7fffc40171c0, timeout=<optimized out>, context=0x5555558f41a0) at gmain.c:4228
#2  g_main_context_iterate (context=0x5555558f41a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3924
#3  0x00007ffff2bc74e2 in g_main_loop_run (loop=0x5555558f4130) at gmain.c:4125
#4  0x00007ffff31ab946 in gdbus_shared_thread_func (user_data=0x5555558f4170) at gdbusprivate.c:247
#5  0x00007ffff2beeb03 in g_thread_proxy (data=0x5555558f72d0) at gthread.c:784
#6  0x00007ffff25ff6ca in start_thread (arg=0x7fffd22de700) at pthread_create.c:333
#7  0x00007ffff2339f6f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7fffd2adf700 (LWP 9712)):
#0  0x00007ffff232e00d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007ffff2bc7156 in g_main_context_poll (priority=<optimized out>, n_fds=2, fds=0x7fffcc0008c0, timeout=<optimized out>, context=0x555555908b50) at gmain.c:4228
#2  g_main_context_iterate (context=context@entry=0x555555908b50, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3924
#3  0x00007ffff2bc726c in g_main_context_iteration (context=0x555555908b50, may_block=may_block@entry=1) at gmain.c:3990
#4  0x00007ffff2bc72b1 in glib_worker_main (data=<optimized out>) at gmain.c:5783
#5  0x00007ffff2beeb03 in g_thread_proxy (data=0x5555558f7280) at gthread.c:784
#6  0x00007ffff25ff6ca in start_thread (arg=0x7fffd2adf700) at pthread_create.c:333
#7  0x00007ffff2339f6f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7ffff7ed9000 (LWP 9696)):
#0  0x00007ffff7764ad9 in vnc_connection_open_host_internal (conn=0x5555565e0590) at vncconnection.c:5404
#1  vnc_connection_coroutine (opaque=<optimized out>) at vncconnection.c:5448
#2  0x00007ffff776726b in coroutine_trampoline (cc=0x5555565dca20) at coroutine_ucontext.c:55
#3  0x00007ffff227cc00 in ?? () from /lib64/libc.so.6
#4  0x00005555565dcde8 in ?? ()
#5  0x0000000000000000 in ?? ()
(gdb)

Comment 1 Jakub Filak 2016-12-01 18:22:09 UTC
The backtrace is unusable because the frames #3 #4 #5 of Thread 1 are unresolved even though you have installed all the debug info. This might mean that the process corrupted its own memory. It's great you didn't give it up and analyzed the core dump file on your own. That's exactly how it should work. It's up to you if you open a new bugzilla bug for the crash. It must be up to the user, because this core cannot be automatically analyzed.

Is there anything else we can do to help you with reporting corrupted core dump files?

Comment 2 Mikhail 2016-12-13 06:15:48 UTC
> The backtrace is unusable because the frames #3 #4 #5 of Thread 1 are unresolved even though you have installed all the debug info.

This situation has put me in a stalemate, because If my backtrace is corrupted as you said, which I can write in bug reports? As I am understand backtrace is useless in this case?

Comment 3 Mikhail 2016-12-13 06:23:28 UTC
> It's up to you if you open a new bugzilla bug for the crash.
It's would be more comfortable if abrt had wizard for this case. And help me for filing useful info.

Comment 4 Fedora End Of Life 2017-11-16 19:16:44 UTC
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.

Comment 5 Fedora End Of Life 2017-12-12 10:04:42 UTC
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.


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