Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Michael Snyder <msnyder@vmware.com>,
	       Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>,
	       "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: next/step after main() function's return
Date: Wed, 29 Dec 2010 03:07:00 -0000	[thread overview]
Message-ID: <20101229030658.GA11911@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <20101229024940.GB2413@adacore.com>

On Wed, 29 Dec 2010 03:49:40 +0100, Joel Brobecker wrote:
> > It can be, depending on the OS:
> [...]
> > fedora-release-14-1.noarch
> > glibc-debuginfo-2.12.90-21.x86_64
> 
> Indeed! Does glic come with debug info by default on Fedora?

Not in a default installation but `debuginfo-install glibc' will provide it.
In fact `debuginfo-install any package' will always provide also glibc due to
the obvious package dependencies.

Also in Fedora GDB there is a rpm-specific patch
	http://pkgs.fedoraproject.org/gitweb/?p=gdb.git;a=blob_plain;f=gdb-6.6-buildid-locate-rpm.patch;hb=master
on top of
	[patch 1/2] build id
	http://sourceware.org/ml/gdb-patches/2010-11/msg00353.html
providing a suggestion:
	gdb-7.2-26.fc14.x86_64
	$ echo 'main(){}' | gcc -x c -; gdb -q ./a.out -ex start
	Temporary breakpoint 1, 0x0000000000400478 in main ()
	Missing separate debuginfos, use: debuginfo-install glibc-2.12.90-21.x86_64
	(gdb) _
and therefore I guess users may have it commonly installed.


Thanks,
Jan


  reply	other threads:[~2010-12-29  3:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27 22:34 Edjunior Barbosa Machado
2010-12-28  5:21 ` Joel Brobecker
2010-12-28  8:24   ` Jan Kratochvil
2010-12-28 23:02     ` Michael Snyder
2010-12-29  2:26       ` Joel Brobecker
2010-12-29  2:37         ` Jan Kratochvil
2010-12-29  2:49           ` Joel Brobecker
2010-12-29  3:07             ` Jan Kratochvil [this message]
2010-12-29 19:26         ` Michael Snyder
2010-12-28 23:05 ` Michael Snyder
2010-12-29  3:58   ` Edjunior Barbosa Machado

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101229030658.GA11911@host1.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=emachado@linux.vnet.ibm.com \
    --cc=gdb@sourceware.org \
    --cc=msnyder@vmware.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox