-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/28/2011 04:16 PM, Paul Allen Newell wrote:
> Community:
>
> I am trying to run gdb on a program that is crashing and I am getting
> messages of:
> +++
> Missing separate debuginfos, use debug-install glibc-2.13.2.x86_64
> libgcc-4.5.1.fc14.x86_64 libg++-4.5.1.fc14.x86_64
> libstdc++-4.5.1.fc14.x86_64
> ---
>
> Googling is not giving me anything that I either understand or trust.
> Querying yum with -list isn't giving me any insight.
>
> Is this message asking me to add something to the compile line or
> something to gdb? And, in either case, what is it asking for.
binaries and the associated debugging information (necessary for productively
running gdb) are distributed as 2 separate rpms. foo and foo-debuginfo
The above message(s) are telling you (in so many words) that you need to install
some debuginfo rpms, and in fact it is also telling you the command line to use
to obtain those debuginfo rpms and install the,
specifically, the diagnostic is asking you to type the following:
debug-install glibc-2.13.2.x86_64 libgcc-4.5.1.fc14.x86_64
libg++-4.5.1.fc14.x86_64 libstdc++-4.5.1.fc14.x86_64
which will download and install the debuginfo rpms for glibc and the stdc++
librarys.
(this pre-supposes that you have standard yum setup, so that you will
automatically find the debuginfo packages, which are not downloaded and
installed by default).
This particular instance will, for example, allow you to step thru glibc (and/or
stdc++) set breakpoints within the libraries, etc.
now. Having said that... It is not always absolutely necessary to install the
library debuginfo's -- it all depends upon whether you are "ok" with not being
able to step into, and set breakpoints in those libraries. i'm usually only
interested in setting breakpoints in *my* code, for example, and usually do not
install the debuginfo libraries for many of the associated libraries that my
application links against. It's a judgement call.
If this is your first time, perhaps don't install the debuginfo for libraries
where you think the problem isn't, and where you think you will not need to
trace into said library(s). If, during debugging, you feel that "gee, it would
be useful to set a breakpoint into that library, and see what's going on", then
install the debuginfo for that library, and restart the debugger and your
application.
All the best,
- -Greg
> I'm hoping someone on this list has run into this debugging C++ and can
> clue me into where I need to look.
>
> Thanks in advance,
> Paul
- --
+---------------------------------------------------------------------+
Please also check the log file at "/dev/null" for additional information.
(from /var/log/Xorg.setup.log)
| Greg Hosler ghosler@xxxxxxxxxx |
+---------------------------------------------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk7Zy9EACgkQ404fl/0CV/RXoQCgnbWtoWMk+mef9S8b9I3IHofV
WUUAmwd2MB4gQ4sgEQKRr6OmRluUgD8A
=i5Rq
-----END PGP SIGNATURE-----
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
