Linux Archive

Linux Archive (http://www.linux-archive.org/)
-   Fedora Development (http://www.linux-archive.org/fedora-development/)
-   -   Why does gdb now give lots of warnings? (http://www.linux-archive.org/fedora-development/28673-why-does-gdb-now-give-lots-warnings.html)

Andrew Haley 01-04-2008 01:52 PM

Why does gdb now give lots of warnings?
 
Neal Becker writes:
> Here is an example:
>
> Starting program: /usr/bin/python
>
> warning: Missing the separate debug info file: /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug

You haven't installed the -debug packages for the shared libs you've
loaded. Telling you this isn't a bug.

What *is* a bug, IMO, is that you can't tell which shared libs it's
complaining about.

Andrew.

--
Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, UK
Registered in England and Wales No. 3798903

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Matthew Miller 01-04-2008 02:49 PM

Why does gdb now give lots of warnings?
 
On Fri, Jan 04, 2008 at 02:52:11PM +0000, Andrew Haley wrote:
> > warning: Missing the separate debug info file: /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug
> You haven't installed the -debug packages for the shared libs you've
> loaded. Telling you this isn't a bug.
> What *is* a bug, IMO, is that you can't tell which shared libs it's
> complaining about.

I agree that that's annoying, but you can just enable the debuginfo repo and
then yum install the given missing filename. Yum will work out which package
provides it.

--
Matthew Miller mattdm@mattdm.org <http://mattdm.org/>
Boston University Linux ------> <http://linux.bu.edu/>

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Jesse Keating 01-04-2008 02:57 PM

Why does gdb now give lots of warnings?
 
On Fri, 4 Jan 2008 10:49:15 -0500
Matthew Miller <mattdm@mattdm.org> wrote:

> I agree that that's annoying, but you can just enable the debuginfo
> repo and then yum install the given missing filename. Yum will work
> out which package provides it.

You can also just use debuginfo-install <appname> and it will enable
the repo for you and track down all the needed debuginfo packages.

--
Jesse Keating
Fedora -- All my bits are free, are yours?
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Jan Kratochvil 01-04-2008 03:12 PM

Why does gdb now give lots of warnings?
 
On Fri, 04 Jan 2008 16:57:20 +0100, Jesse Keating wrote:
> On Fri, 4 Jan 2008 10:49:15 -0500
> Matthew Miller <mattdm@mattdm.org> wrote:
>
> > I agree that that's annoying, but you can just enable the debuginfo
> > repo and then yum install the given missing filename. Yum will work
> > out which package provides it.
>
> You can also just use debuginfo-install <appname> and it will enable
> the repo for you and track down all the needed debuginfo packages.

$ ls -l /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug
lrwxrwxrwx 1 root root 27 2007-10-21 15:58 /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug -> ../../lib64/ld-2.7.so.debug*
tells the name of the already installed library missing its -debuginfo.

$ repoquery -qf /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug
glibc-debuginfo-0:2.7-2.x86_64
tells the -debuginfo package name needing to be installed.

# yum install /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug
installs the missing -debuginfo package.

The library name was omitted intentionally there as the printed lines are
already too long just to be able to provide the .debug filename required for
`yum install'.

People commonly try to debug with GDB without having the -debuginfo packages
installed so I expected some hint may be useful there.

`debuginfo-install <appname>' may not install the matching -debuginfo version,
there may be multiple simultaneous -debuginfo versions available and/or
installed in the future (F9?).

I am open for some more convenient interface - currently going to print also
the shared library name there. (GDB cannot print anything about rpms.)


Thanks,
Jan

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Andrew Haley 01-04-2008 03:19 PM

Why does gdb now give lots of warnings?
 
Jan Kratochvil writes:
> On Fri, 04 Jan 2008 16:57:20 +0100, Jesse Keating wrote:
> > On Fri, 4 Jan 2008 10:49:15 -0500
> > Matthew Miller <mattdm@mattdm.org> wrote:
> >
> > > I agree that that's annoying, but you can just enable the debuginfo
> > > repo and then yum install the given missing filename. Yum will work
> > > out which package provides it.
> >
> > You can also just use debuginfo-install <appname> and it will enable
> > the repo for you and track down all the needed debuginfo packages.
>
> $ ls -l /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug
> lrwxrwxrwx 1 root root 27 2007-10-21 15:58 /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug -> ../../lib64/ld-2.7.so.debug*
> tells the name of the already installed library missing its -debuginfo.
>
> $ repoquery -qf /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug
> glibc-debuginfo-0:2.7-2.x86_64
> tells the -debuginfo package name needing to be installed.
>
> # yum install /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug
> installs the missing -debuginfo package.
>
> The library name was omitted intentionally there as the printed lines are
> already too long just to be able to provide the .debug filename required for
> `yum install'.
>
> People commonly try to debug with GDB without having the -debuginfo packages
> installed so I expected some hint may be useful there.
>
> `debuginfo-install <appname>' may not install the matching -debuginfo version,
> there may be multiple simultaneous -debuginfo versions available and/or
> installed in the future (F9?).
>
> I am open for some more convenient interface - currently going to print also
> the shared library name there.

That would do it. Something really simple like "Missing debuginfo for
shared object XXXXglibc.soXXX".

> (GDB cannot print anything about rpms.)

I'll take your word for that.

Andrew.

--
Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, UK
Registered in England and Wales No. 3798903

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Jan Kratochvil 01-04-2008 03:47 PM

Why does gdb now give lots of warnings?
 
On Fri, 04 Jan 2008 17:19:42 +0100, Andrew Haley wrote:
> Jan Kratochvil writes:
...
> > I am open for some more convenient interface - currently going to print also
> > the shared library name there.
>
> That would do it. Something really simple like "Missing debuginfo for
> shared object XXXXglibc.soXXX".

Suggesting this one?
Missing debuginfo for shared object ld-linux-x86-64.so.2

There is no easy chance how to install the associated debuginfos using YUM from
such messages. And `debuginfo-install <appname>' will not work in all cases
- at least not fot dlopen()ed libraries - such as the 'nss*' packages.

Printing the rpm Provides keyword would make it already RPM/Fedora specific
Missing debuginfo for shared object ld-linux-x86-64.so.2()(64bit)
and still deriving the -debuginfo package name from it is not easy enough.


Possibly printing
warning: Missing the separate debug info file: /usr/lib/debug/lib64/ld-linux-x86-64.so.2.debug
may be more convenient while still usable for YUM?


It would still print
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug
if the .debug file exists but it is not matching the required version
- otherwise that would contradict the purpose of the F8 `build-id' feature
http://fedoraproject.org/wiki/Releases/FeatureBuildId


> > (GDB cannot print anything about rpms.)
>
> I'll take your word for that.

OK, you are right Fedora GDB could; the build-id support messages should be
cross-OS ones, this loading feature is still not imported into upstream GDB and
it is heading there.



Thanks,
Jan

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Andrew Haley 01-04-2008 03:53 PM

Why does gdb now give lots of warnings?
 
Jan Kratochvil writes:
> On Fri, 04 Jan 2008 17:19:42 +0100, Andrew Haley wrote:
> > Jan Kratochvil writes:
> ...
> > > I am open for some more convenient interface - currently going to print also
> > > the shared library name there.
> >
> > That would do it. Something really simple like "Missing debuginfo for
> > shared object XXXXglibc.soXXX".
>
> Suggesting this one?
> Missing debuginfo for shared object ld-linux-x86-64.so.2
>
> There is no easy chance how to install the associated debuginfos using YUM from
> such messages. And `debuginfo-install <appname>' will not work in all cases
> - at least not fot dlopen()ed libraries - such as the 'nss*' packages.
>
> Printing the rpm Provides keyword would make it already RPM/Fedora specific
> Missing debuginfo for shared object ld-linux-x86-64.so.2()(64bit)
> and still deriving the -debuginfo package name from it is not easy enough.
>
>
> Possibly printing
> warning: Missing the separate debug info file: /usr/lib/debug/lib64/ld-linux-x86-64.so.2.debug
> may be more convenient while still usable for YUM?
>
>
> It would still print
> warning: Missing the separate debug info file: /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug
> if the .debug file exists but it is not matching the required version
> - otherwise that would contradict the purpose of the F8 `build-id' feature
> http://fedoraproject.org/wiki/Releases/FeatureBuildId
>
>
> > > (GDB cannot print anything about rpms.)
> >
> > I'll take your word for that.
>
> OK, you are right Fedora GDB could; the build-id support messages should be
> cross-OS ones, this loading feature is still not imported into upstream GDB and
> it is heading there.

Sure, but we could have a simple local message like

Try "yum install /usr/lib/debug/.build-id/72/67a2ecd318b0f87a0747a6986d0d6dc01c6d8d.debug"

I learnt only today that would work...

Andrew.

--
Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, UK
Registered in England and Wales No. 3798903

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Jan Kratochvil 01-04-2008 04:08 PM

Why does gdb now give lots of warnings?
 
On Fri, 04 Jan 2008 17:53:09 +0100, Andrew Haley wrote:
> Jan Kratochvil writes:
...
> > OK, you are right Fedora GDB could; the build-id support messages should be
> > cross-OS ones, this loading feature is still not imported into upstream GDB and
> > it is heading there.
>
> Sure, but we could have a simple local message like
>
> Try "yum install /usr/lib/debug/.build-id/72/67a2ecd318b0f87a0747a6986d0d6dc01c6d8d.debug"
>
> I learnt only today that would work...

Such as this one - just for the first such message printed? I guess changing
the `Missing ...' message itself would be already too OS-specific.

Starting program: /usr/bin/python

Try: yum install /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug

warning: Missing the separate debug info file: /usr/lib/debug/.build-id/e8/abaa654dc4b17b75c06c866898a17ea06f2bcf.debug
[Thread debugging using libthread_db enabled]
[New process 16964]

warning: Missing the separate debug info file: /usr/lib/debug/.build-id/96/c005fcc474ab8b0d1aa41267111de2f0b647b0.debug

warning: Missing the separate debug info file: /usr/lib/debug/.build-id/cd/19bdc5e57f1a00b2c7b4d6c6d1e3882d199ef9.debug

warning: Missing the separate debug info file: /usr/lib/debug/.build-id/72/0ad477c75be7d7cbc97c0a6f443746dda98341.debug

warning: Missing the separate debug info file: /usr/lib/debug/.build-id/ea/5b2fb654311e2dc8beacf2f19c1c6d172ba93d.debug

...


Also removing the empty line (despite it may occasionally start in half of the
screen) may help, I guess.


Any other messaging feedback is welcome before it goes upstream.



Thanks,
Jan

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Andrew Haley 01-04-2008 04:15 PM

Why does gdb now give lots of warnings?
 
Jan Kratochvil writes:
> On Fri, 04 Jan 2008 17:53:09 +0100, Andrew Haley wrote:
> > Jan Kratochvil writes:
> ...
> > > OK, you are right Fedora GDB could; the build-id support messages should be
> > > cross-OS ones, this loading feature is still not imported into upstream GDB and
> > > it is heading there.
> >
> > Sure, but we could have a simple local message like
> >
> > Try "yum install /usr/lib/debug/.build-id/72/67a2ecd318b0f87a0747a6986d0d6dc01c6d8d.debug"
> >
> > I learnt only today that would work...
>
> Such as this one - just for the first such message printed? I guess changing
> the `Missing ...' message itself would be already too OS-specific.

Perfection would be:

Missing debuginfo for /lib64/libnss_files-2.7.so
Try "yum install /usr/lib/debug/.build-id/72/67a2ecd318b0f87a0747a6986d0d6dc01c6d8d.debug"

If we can't do that upstream, then the closer we get, the better. Or
we have a local patch.


> Starting program: /usr/bin/python
>
> Try: yum install /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug
> warning: Missing the separate debug info file: /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug
>
> warning: Missing the separate debug info file: /usr/lib/debug/.build-id/e8/abaa654dc4b17b75c06c866898a17ea06f2bcf.debug
> [Thread debugging using libthread_db enabled]
> [New process 16964]
>
> warning: Missing the separate debug info file: /usr/lib/debug/.build-id/96/c005fcc474ab8b0d1aa41267111de2f0b647b0.debug
>
> warning: Missing the separate debug info file: /usr/lib/debug/.build-id/cd/19bdc5e57f1a00b2c7b4d6c6d1e3882d199ef9.debug
>
> warning: Missing the separate debug info file: /usr/lib/debug/.build-id/72/0ad477c75be7d7cbc97c0a6f443746dda98341.debug
>
> warning: Missing the separate debug info file: /usr/lib/debug/.build-id/ea/5b2fb654311e2dc8beacf2f19c1c6d172ba93d.debug
>
> ...
>
>
> Also removing the empty line (despite it may occasionally start in half of the
> screen) may help, I guess.

It would.

Andrew.

--
Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, UK
Registered in England and Wales No. 3798903

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Jan Kratochvil 01-04-2008 04:31 PM

Why does gdb now give lots of warnings?
 
On Fri, 04 Jan 2008 18:15:00 +0100, Andrew Haley wrote:
...
> Perfection would be:
>
> Missing debuginfo for /lib64/libnss_files-2.7.so
> Try "yum install /usr/lib/debug/.build-id/72/67a2ecd318b0f87a0747a6986d0d6dc01c6d8d.debug"

Such two-line message for each such missing file? OK.


> If we can't do that upstream, then the closer we get, the better. Or
> we have a local patch.

Sure `yum install' is not acceptable upstream. Local patch changing the
wording a bit would be fine (configure.in detection of each specific
OS/installing-tool is IMO not appropriate upstream).


Accepted, F8/F9 update should be fine.


Thanks,
Jan

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list


All times are GMT. The time now is 07:10 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.