Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Steven Johnson <sjohnson@sakuraindustries.com>
Cc: Frederic RISS <frederic.riss@st.com>,
		Jim Blandy <jimb@codesourcery.com>,
	gdb@sources.redhat.com
Subject: Re: Problems with startup code symbols (Copious warnings)
Date: Tue, 20 Jun 2006 23:35:00 -0000	[thread overview]
Message-ID: <20060620233444.GA14292@nevyn.them.org> (raw)
In-Reply-To: <449856E1.50308@sakuraindustries.com>

On Wed, Jun 21, 2006 at 07:13:21AM +1100, Steven Johnson wrote:
> Is it possible to to tell what section the debug info is for?

No, at this point, that's exactly the problem.  The necessary
information is gone.

Long term, the correct fix to this is not in GDB anyway.  Both linker
and compiler fixes have been pursued.  Someone just needs to push
through on it.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-06-20 23:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08  7:23 Steven Johnson
2006-06-08  9:06 ` Jim Blandy
2006-06-08 12:25   ` Steven Johnson
2006-06-08 23:10     ` Steven Johnson
2006-06-15  0:12     ` Jim Blandy
2006-06-15  7:33       ` Jim Blandy
2006-06-19  9:36         ` Frederic RISS
2006-06-20 12:23           ` Daniel Jacobowitz
2006-06-20 12:33             ` Frederic RISS
2006-06-20 12:56               ` Daniel Jacobowitz
2006-06-20 13:09                 ` Frederic RISS
2006-06-20 20:17                   ` Steven Johnson
2006-06-20 23:35                     ` Daniel Jacobowitz [this message]
2006-06-21  8:54                       ` Frederic RISS
2006-06-21 14:44                         ` Steven Johnson
2006-06-21 15:28                         ` Daniel Jacobowitz
2006-06-19 10:00         ` Steven Johnson

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=20060620233444.GA14292@nevyn.them.org \
    --to=drow@false.org \
    --cc=frederic.riss@st.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@codesourcery.com \
    --cc=sjohnson@sakuraindustries.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