[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GNU Linker Utility Assert
From: |
Charles_Triemstra |
Subject: |
Re: GNU Linker Utility Assert |
Date: |
Fri, 22 Mar 2002 09:01:23 -0500 |
Hi Tom.
I have attached the test case.
(See attached file: ldassert.tar)
For me, at least having the name of the symbol displayed would have helped
pin-point what I needed to change to have the link
complete.
/Chuck
Tom Rix <address@hidden>@cygnus.com on 03/22/2002 09:42:47 AM
Sent by: address@hidden
To: Nick Clifton <address@hidden>
cc: address@hidden, address@hidden, address@hidden,
address@hidden, address@hidden,
address@hidden
Subject: Re: GNU Linker Utility Assert
Nick Clifton wrote:
> Hi Tom,
>
> > It seems to me that a better place to catch this problem would be
> > the assembler.
>
> True - but it would still be nice if the linker could provide a
> helpful error message instead of an assertion failure.
>
Yes. I agree.
Changing the linker assertion is fine but the message needs to be
changed since this is more a problem with an invalid function descriptor
symbol than a relocation. I will take care of it.
Symbol creation problems should be caught in the assembler.
To make sure the correct problem is fixed I need a testcase.
Tom
--
Tom Rix
GCC Engineer
address@hidden
ldassert.tar
Description: Binary data
- Re: GNU Linker Utility Assert,
Charles_Triemstra <=