Re: What happened to quality debuginfo?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Nov 2, 2020 at 5:23 pm, Keith Seitz <keiths@xxxxxxxxxx> wrote:
In the meantime, does using debuginfod work?

export DEBUGINFOD_URLS=https://debuginfod.elfutils.org

Setting this in your env /should/ cause any missing debuginfo to be automatically downloaded (by just about any tool requiring debuginfo, e.g, gdb, binutils)

Hm, it sort of works. For a test, I launch gnome-calculator, hit Ctrl+C once it loads, and generate a backtrace. I see it used existing debuginfo for glibc, but didn't download anything for glib:

$ export DEBUGINFOD_URLS=https://debuginfod.elfutils.org
$ gdb gnome-calculator
GNU gdb (GDB) Fedora 9.2-7.fc33
Copyright (C) 2020 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 gnome-calculator...
Reading symbols from .gnu_debugdata for /usr/bin/gnome-calculator...
(No debugging symbols found in .gnu_debugdata for /usr/bin/gnome-calculator)
(gdb) bt full
No stack.
(gdb) r
Starting program: /usr/bin/gnome-calculator
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffe7f14640 (LWP 36182)]
[New Thread 0x7fffe7713640 (LWP 36183)]
[New Thread 0x7fffe6d79640 (LWP 36202)]
[New Thread 0x7fffe5883640 (LWP 36205)]
[New Thread 0x7fffe5082640 (LWP 36206)]
[Thread 0x7fffe5082640 (LWP 36206) exited]
^C
Thread 1 "gnome-calculato" received signal SIGINT, Interrupt.
0x00007ffff6d32a0f in __GI___poll (fds=0x555555617b20, nfds=3, timeout=13135)
   at ../sysdeps/unix/sysv/linux/poll.c:29
29 return SYSCALL_CANCEL (poll, fds, nfds, timeout);
(gdb) bt full
#0 0x00007ffff6d32a0f in __GI___poll
   (fds=0x555555617b20, nfds=3, timeout=13135)
   at ../sysdeps/unix/sysv/linux/poll.c:29
       sc_ret = -516
       sc_cancel_oldtype = 0
#1 0x00007ffff7f1dd1e in g_main_context_iterate.constprop ()
   at /lib64/libglib-2.0.so.0
#2 0x00007ffff7eca41f in g_main_context_iteration ()
   at /lib64/libglib-2.0.so.0
#3 0x00007ffff746d3e5 in g_application_run () at /lib64/libgio-2.0.so.0
#4 0x0000555555562162 in main ()

So that is a fail.

Next test: launch gnome-calculator without gdb, run 'killall -SEGV gnome-calculator', and then run 'coredumpctl gdb' and 'bt full'. Result is the same: no debuginfo for glib.

Third test: run gnome-calculator, and while running, 'gdb -p `pidof gnome-calculator`. Result is the same: no debuginfo for glib.

I do see that it is capable of downloading some debuginfo. E.g. when I attached to goa-daemon, I saw:

Downloading separate debug info for /lib64/libc.so.6...
Downloading separate debug info for /lib64/libpthread.so.0...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
--Type <RET> for more, q to quit, c to continue without paging--c
Downloading separate debug info for /lib64/libresolv.so.2...
Downloading separate debug info for /lib64/ld-linux-x86-64.so.2...
Downloading separate debug info for /lib64/librt.so.1...
Downloading separate debug info for /lib64/libsystemd.so.0...
Downloading separate debug info for /home/mcatanzaro/.cache/debuginfod_client/78dab7efffc09e12cb1d33fec9e0e4fd0a0b974a/debuginfo...
Downloading separate debug info for /lib64/libdl.so.2...
Downloading separate debug info for /lib64/libstdc++.so.6...
Downloading separate debug info for /home/mcatanzaro/.cache/debuginfod_client/8a631bbf2acdfdaf554335bb9e8a04dd4e3e9c17/debuginfo...
Downloading separate debug info for /lib64/libm.so.6...
Downloading separate debug info for /lib64/libgcc_s.so.1...
Downloading separate debug info for /lib64/libdw.so.1...
Downloading separate debug info for /home/mcatanzaro/.cache/debuginfod_client/e32142f3e8a9c7834dba57d6f2d7e082744876e9/debuginfo...
Downloading separate debug info for /lib64/libelf.so.1...
Downloading separate debug info for /lib64/libdebuginfod-0.181.so...
Downloading separate debug info for /lib64/libnss_files.so.2...
Downloading separate debug info for /lib64/libnss_resolve.so.2...
Downloading separate debug info for /home/mcatanzaro/system-supplied DSO at 0x7fff9d56b000...

That's cool. But again, no debuginfo for glib, sadly:

#0 0x00007f0211851a0f in __GI___poll (fds=0x55f9b84074f0, nfds=2, timeout=-1)
   at ../sysdeps/unix/sysv/linux/poll.c:29
       sc_ret = -516
       sc_cancel_oldtype = 0
#1 0x00007f02119c9d1e in g_main_context_iterate.constprop ()
   at /lib64/libglib-2.0.so.0
#2 0x00007f02119786ab in g_main_loop_run () at /lib64/libglib-2.0.so.0
#3 0x000055f9b66c6d52 in main ()

I tried one final test with epiphany, but there are no debug symbols for Epiphany itself either:

$ gdb epiphany
GNU gdb (GDB) Fedora 9.2-7.fc33
Copyright (C) 2020 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 epiphany...
Reading symbols from .gnu_debugdata for /usr/bin/epiphany...
(No debugging symbols found in .gnu_debugdata for /usr/bin/epiphany)
(gdb) break ephy_embed_shell_init
Breakpoint 1 at 0x1bf90
(gdb) r
Starting program: /usr/bin/epiphany
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffe01d5640 (LWP 37886)]
[New Thread 0x7fffdf9d4640 (LWP 37887)]
[New Thread 0x7fffde7cc640 (LWP 37994)]

Thread 1 "epiphany" hit Breakpoint 1, 0x000055555556ff90 in ephy_embed_shell_init ()
(gdb) bt full
#0 0x000055555556ff90 in ephy_embed_shell_init ()
#1 0x00007ffff7146977 in g_type_create_instance ()
   at /lib64/libgobject-2.0.so.0
#2 0x00007ffff712fc05 in g_object_new_internal ()
   at /lib64/libgobject-2.0.so.0
#3 0x00007ffff71312a4 in g_object_new_valist () at /lib64/libgobject-2.0.so.0
#4 0x00007ffff7131609 in g_object_new () at /lib64/libgobject-2.0.so.0
#5 0x00007ffff7f46e72 in _ephy_shell_create_instance ()
   at /usr/lib64/epiphany/libephymain.so
#6 0x000055555556f9b6 in main ()

So I'm afraid this is another fail. Are there known issues here?

Michael

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux