This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: collect2, weak functions and .debug_line section.


On Thu, Oct 16, 2003 at 03:00:58PM -0400, Jason Merrill wrote:
> On Thu, 16 Oct 2003 11:58:14 -0400, Daniel Jacobowitz <drow@mvista.com> wrote:
> 
> > On Thu, Oct 16, 2003 at 05:55:24PM +0200, Carlo Wood wrote:
> >> There is a problem with debug information being used
> >> from one object file and the assembly code from another
> >> object file (both containing the "same" function)
> >> that do not completely match, with screwed debug
> >> info as a result.
> >
> >> I am not sure how to report this in GNATS.
> >> What component would this belong to?
> >> Heh - I don't even know which mailinglist this belongs to :/
> >> 
> >> Does anyone have ideas of how to fix this?
> >
> > Search the archives for more.  I believe that the proper fix is to use
> > ELF section groups, but I don't know much about the details.  One of
> > the bodies should be discarded, and its debug info should be discarded
> > also.
> 
> Yes.  But I don't see why there would be a problem with the current
> situation; only the right .debug_line info should match the current PC.

I believe the problem is not with inlining, but with one copy being
discarded?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]