From: Elena Zannoni <ezannoni@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Jim Blandy <jimb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc;rfa:symtab] Deprecate inside_entry_file
Date: Thu, 11 Sep 2003 23:45:00 -0000 [thread overview]
Message-ID: <16225.2845.592851.597277@localhost.redhat.com> (raw)
In-Reply-To: <3F5F65CB.4070605@redhat.com>
Andrew Cagney writes:
> > Andrew Cagney <ac131313@redhat.com> writes:
> >
> >> Before thinking about committing this I'd like to see comments on the
> >> symtab side.
> >
> >
> > The changes in mdebugread.c, dwarfread.c, dwarf2read.c, dbxread.c, and
> > coffread.c are just renamings. Was there something more specific that
> > you wanted reviewed?
>
> I wrote:
>
> > This patch deprecates both the function inside_entry_file() and the object file variables that support it (I don't want there to be any confusion over this :-).
>
> Are the symtab maintainers ok with this?
>
> Andrew
>
In particular note that the function:
symfile.c:init_entry_point_info() which sets up all the
objfile->ei.deprecated_entry_file* is seriously screwed up for PIE
files anyway.
In such a case we need to figure out where the program got loaded,
just like a shlib, the main executable is not marked as EXEC in the
elf header anymore, and lots of other fun stuff. Anyway, the way the
entry file/entry point stuff is handled now won't work for PIE.
I am currently working on PIE support, BTW. I'll post something as
soon as I have some coherent story.
elena
next prev parent reply other threads:[~2003-09-11 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 23:19 Andrew Cagney
2003-09-10 17:19 ` Jim Blandy
2003-09-10 17:56 ` Andrew Cagney
2003-09-11 21:55 ` Jim Blandy
2003-09-11 23:45 ` Elena Zannoni [this message]
2003-09-12 18:52 ` Andrew Cagney
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=16225.2845.592851.597277@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.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