public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/11704] Cannot load debugging info
Date: Mon, 14 Jun 2010 20:58:00 -0000	[thread overview]
Message-ID: <20100614205841.22424.qmail@sourceware.org> (raw)
In-Reply-To: <20100614182907.11704.dimabarts@yahoo.com>


------- Additional Comments From tromey at redhat dot com  2010-06-14 20:58 -------
> % cc hello.o -o hello

Try changing that to:

cc hello.o -g -o hello

I think you need -g on the link line to tell the linker to preserve debuginfo.

You can always check gdb here by using readelf or something like that to
see if the executable does in fact have debuginfo.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at redhat dot com
             Status|UNCONFIRMED                 |WAITING


http://sourceware.org/bugzilla/show_bug.cgi?id=11704

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  reply	other threads:[~2010-06-14 20:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-14 18:29 [Bug gdb/11704] New: " dimabarts at yahoo dot com
2010-06-14 20:58 ` tromey at redhat dot com [this message]
2010-06-14 21:22 ` [Bug gdb/11704] " dimabarts at yahoo dot com
2010-06-15 21:46 ` tromey at redhat dot com
2010-06-16  0:35 ` dimabarts at yahoo dot com
2010-06-16 17:38 ` dimabarts at yahoo dot com
2010-06-17 17:03 ` tromey at redhat dot com
     [not found] <bug-11704-4717@http.sourceware.org/bugzilla/>
2014-09-12 22:21 ` sergiodj at redhat dot com

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=20100614205841.22424.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).