From: Steven Johnson <sjohnson@sakuraindustries.com>
To: Daniel Jacobowitz <drow@false.org>
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: Wed, 21 Jun 2006 14:44:00 -0000 [thread overview]
Message-ID: <44990926.3070106@sakuraindustries.com> (raw)
In-Reply-To: <1150877429.2480.91.camel@crx549.cro.st.com>
Frederic RISS wrote:
>On Tue, 2006-06-20 at 19:34 -0400, Daniel Jacobowitz wrote:
>
>
>>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.
>>
>>
>>
Ok, from my poking around it seemed that what was still known however
was the file name the symbol comes from (correct?). Again, it would
seem unlikely that code from a file starting at 0, would also contain
code trigerring link once behaviour. So, what about (until a better fix
comes along) a settable variable that is the name of a file to ignore
the "discard symbols for link once sections" behaviour?
Something like:
set this-file-validly-starts-at-zero vectors.S
As we are talking about a single problematic address, a single option
should be all that's required, as 2 files can't both start at the same
address (assuming no one has overlays going on at address 0).
If this is acceptable, id like it if anyone can propose a more suitable
name for the option as I'm stumped for a decent one.
This is something I AM comfortable in adding to GDB, Docs, etc. And
will happilly do it by this weekend, if its OK with everyone concerned.
>>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.
>>
>>
>
>Just out of curiosity, do you have any pointers to these 'pursued
>fixes'?
>
>
I too would be interested in pointers to this.
Steven J
next prev parent reply other threads:[~2006-06-21 8:54 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
2006-06-21 8:54 ` Frederic RISS
2006-06-21 14:44 ` Steven Johnson [this message]
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=44990926.3070106@sakuraindustries.com \
--to=sjohnson@sakuraindustries.com \
--cc=drow@false.org \
--cc=frederic.riss@st.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@codesourcery.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