[TUHS] Debugging help sought

[Warner Losh]

On Wed, Aug 5, 2020, 9:04 PM Warner Losh <imp at bsdimp.com> wrote:

>
>
> On Wed, Aug 5, 2020, 8:12 PM Jim Capp <jcapp at anteil.com> wrote:
>
>> Looking through the code, I see some awfully long function names.   Does
>> anyone recall if there are/were limits on the size of variable and function
>> names?
>>
>
> 8 I think was the limit.
>
> Could that cause this error?
>>
>
> Maybe too many symbols?
>
> The error comes from lookloc. This is called for external type
> relocations. It searches the local symbol table for something that matches
> the relocation entry. This error happens when it can't find it...
>
> Not sure of the root causes for *that* though.
>

Try cc -c and do size on the .o. that might give you a hint about what is
too big.

Warner

Warner
>
>> On Aug 5, 2020, at 9:30 PM, Adam Thornton <athornton at gmail.com> wrote:
>>
>> 
>> I finally munged lbforth.c (https://gist.github.com/lbruder/10007431)
>> into compiling cleanly on mostly-stock v7 with the system compiler (lbforth
>> itself does fine on 211BSD, but it needs a little help to build in a real
>> K&R environment).
>>
>> Which would be nice, except that when it gets to the linker....
>>
>> $ cc -o 4th forth.c
>> ld:forth.o: Local symbol botch
>>
>> WTF?
>>
>> How do I begin to debug this?
>>
>> Adam
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20200805/fa2ac9da/attachment.htm>