Description of problem: I've let run the automatic crash reporter on a crash related to akonadi, but gdb itself segfault'd while doing so. Version-Release number of selected component: gdb-headless-8.1-15.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/libexec/gdb -batch -iex add-auto-load-safe-path /var/cache/abrt-di/usr/lib/debug -iex add-auto-load-scripts-directory /var/cache/abrt-di/usr/lib/debug -ex set debug-file-directory /usr/lib/debug:/var/cache/abrt-di/usr/lib/debug -ex file /usr/bin/akonadiconsole -ex core-file ./coredump -ex thread apply all -ascending backtrace 1024 full -ex info sharedlib -ex print (char*)__abort_msg -ex print (char*)__glib_assert_msg -ex info all-registers -ex disassemble crash_function: value_entirely_covered_by_range_vector executable: /usr/libexec/gdb journald_cursor: s=7ee9eaff05cd45eb8a32e153b6e917d8;i=52d1;b=72faa8541aeb45b7a798e153d3d578b6;m=ec23afded;t=56df8c5fe67ce;x=3dca01d1a5028b3c kernel: 4.16.13-300.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 value_entirely_covered_by_range_vector at ../../gdb/value.c:397 #1 value_entirely_optimized_out at ../../gdb/value.c:422 #2 cp_print_static_field at ../../gdb/cp-valprint.c:631 #3 cp_print_value_fields(type*, type*, long, unsigned long, ui_file*, int, value*, value_print_options const*, type**, int) at ../../gdb/cp-valprint.c:332 #4 cp_print_value_fields_rtti at ../../gdb/cp-valprint.c:449 #5 c_val_print_struct at ../../gdb/c-valprint.c:411 #6 c_val_print at ../../gdb/c-valprint.c:532 #7 val_print(type*, long, unsigned long, ui_file*, int, value*, value_print_options const*, language_defn const*) at ../../gdb/valprint.c:1064 #8 cp_print_value_fields(type*, type*, long, unsigned long, ui_file*, int, value*, value_print_options const*, type**, int) at ../../gdb/cp-valprint.c:356 #9 cp_print_value_fields_rtti at ../../gdb/cp-valprint.c:449 Potential duplicate: bug 1445872
Created attachment 1448311 [details] File: backtrace
Created attachment 1448312 [details] File: cgroup
Created attachment 1448313 [details] File: core_backtrace
Created attachment 1448314 [details] File: cpuinfo
Created attachment 1448315 [details] File: dso_list
Created attachment 1448316 [details] File: environ
Created attachment 1448317 [details] File: exploitable
Created attachment 1448318 [details] File: limits
Created attachment 1448319 [details] File: maps
Created attachment 1448320 [details] File: mountinfo
Created attachment 1448321 [details] File: open_fds
Created attachment 1448322 [details] File: proc_pid_status
Thanks for the report. Would you be able to provide the coredump generated by GDB's crash?
*** Bug 1619220 has been marked as a duplicate of this bug. ***
(In reply to Sergio Durigan Junior from comment #13) > Thanks for the report. Would you be able to provide the coredump generated > by GDB's crash? I no longer have this coredump and I can't reproduce the original issue leading to this.
Thanks, I'm closing this bug then. Feel free to reopen if needed.