From: Warner Losh <imp@bsdimp.com>
To: Jim Capp <jcapp@anteil.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Debugging help sought
Date: Wed, 5 Aug 2020 21:08:45 -0600 [thread overview]
Message-ID: <CANCZdfrtD2n0b3VnP=HHh0TbCOdkWjUFYhvwF0wp675dMY-tbw@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfojWSkL_cJK1ZPKENf6Joc31=uXPpe6oigXkzQ-dR65Bw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
On Wed, Aug 5, 2020, 9:04 PM Warner Losh <imp@bsdimp.com> wrote:
>
>
> On Wed, Aug 5, 2020, 8:12 PM Jim Capp <jcapp@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@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
>>
>>
[-- Attachment #2: Type: text/html, Size: 3237 bytes --]
next prev parent reply other threads:[~2020-08-06 3:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 1:28 Adam Thornton
2020-08-06 2:01 ` Jim Capp
2020-08-06 3:04 ` Warner Losh
2020-08-06 3:08 ` Warner Losh [this message]
2020-08-06 5:55 ` Adam Thornton
2020-08-06 4:57 ` Dave Horsfall
2020-08-06 7:16 ` Otto Moerbeek
2020-08-06 15:47 ` Paul Winalski
2020-08-06 16:09 ` Larry McVoy
2020-08-06 16:19 ` Paul Winalski
2020-08-06 16:24 ` Larry McVoy
2020-08-06 23:41 ` Adam Thornton
2020-08-07 0:35 ` Warner Losh
2020-08-07 4:30 ` Adam Thornton
2020-08-07 5:49 ` Warner Losh
2020-08-07 5:54 ` Adam Thornton
2020-08-07 16:07 Noel Chiappa
2020-08-07 17:11 ` John Cowan
2020-08-07 20:48 ` Warner Losh
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='CANCZdfrtD2n0b3VnP=HHh0TbCOdkWjUFYhvwF0wp675dMY-tbw@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=jcapp@anteil.com \
--cc=tuhs@tuhs.org \
/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;
as well as URLs for NNTP newsgroup(s).