Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #100498

Re: Pine 64

From jacobnavia <jacob@jacob.remcomp.fr>
Newsgroups comp.lang.c
Subject Re: Pine 64
Date 2016-12-28 22:55 +0100
Organization A noiseless patient Spider
Message-ID <o41c9q$aom$1@dont-email.me> (permalink)
References (2 earlier) <o40bmj$q3r$1@dont-email.me> <5863b3c8.11963062@news.xs4all.nl> <o40d27$u77$1@dont-email.me> <lno9zv53gj.fsf@kst-u.example.com> <o418m4$teb$1@dont-email.me>

Show all headers | View raw

Le 28/12/2016 à 21:53, David Brown a écrit :
> And Jacob was talking about compiling C on it, and even compiling his C
> compiler on it, before we got side-tracked.

Yeah, I got to the link phase. I compiled lcc wit gcc, and that compiler 
was used to compile the same code again producing (at last) a bloated 
executable, full of bad code, but an executable nevertheless.

Normal for the first iteration. This process is called boot strapping, 
and it is a PITA, as it is commonly called...

The fact that all the code was translated with a correct assembler 
syntax was a big step. Now, there is a big problem with the debug info.

If I link with the debug info, the linker tells me

stabs index error.

And doesn't produce an executable.

Of course, I would be rather keenly interested in knowing where in the 
1.5 MB of code full of stab statements the error could be???

But the linker will not tell me, why should it?

If you are the developer of the linker and you know only gcc is around 
why bother specifying the module and line number or index of the stab or 
whatever. A sensible error message is too much asking here.

Another problem (solved this one) was the c library. I could not compile 
the headers of gcc, full of strange stuff with __attribute__ whatever. 
But making appropiate #defines solved that problem and I could link, 
albeit without the debug info.

Problem is, I am generating stabs and gcc has changed to dwarf. Do they 
correctly support stabs any more?

If that is the case I would have to rewrite the debugger and use my own 
format. I remember that I had a debugger using the ptrace interface back 
then.

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Pine 64 jacobnavia <jacob@jacob.remcomp.fr> - 2016-12-27 23:44 +0100
  Re: Pine 64 raltbos@xs4all.nl (Richard Bos) - 2016-12-27 22:54 +0000
    Re: Pine 64 jacobnavia <jacob@jacob.remcomp.fr> - 2016-12-28 00:41 +0100
      Re: Pine 64 raltbos@xs4all.nl (Richard Bos) - 2016-12-28 12:14 +0000
    Re: Pine 64 David Brown <david.brown@hesbynett.no> - 2016-12-28 13:39 +0100
      Re: Pine 64 raltbos@xs4all.nl (Richard Bos) - 2016-12-28 12:45 +0000
        Re: Pine 64 David Brown <david.brown@hesbynett.no> - 2016-12-28 14:02 +0100
          Re: Pine 64 Keith Thompson <kst-u@mib.org> - 2016-12-28 10:11 -0800
            Re: Pine 64 Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-12-28 10:50 -0800
            Re: Pine 64 jacobnavia <jacob@jacob.remcomp.fr> - 2016-12-28 22:55 +0100
              Re: Pine 64 David Brown <david.brown@hesbynett.no> - 2016-12-29 12:21 +0100
                Re: Pine 64 jacobnavia <jacob@jacob.remcomp.fr> - 2016-12-29 21:38 +0100
                Re: Pine 64 David Brown <david.brown@hesbynett.no> - 2016-12-30 10:10 +0100
            Re: Pine 64 David Brown <david.brown@hesbynett.no> - 2016-12-28 21:53 +0100
            Re: Pine 64 raltbos@xs4all.nl (Richard Bos) - 2016-12-28 19:54 +0000
  Re: Pine 64 Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2016-12-27 18:03 -0500
    Re: Pine 64 jacobnavia <jacob@jacob.remcomp.fr> - 2016-12-28 00:36 +0100
      Re: Pine 64 Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2016-12-27 18:44 -0500
        Re: Pine 64 jacobnavia <jacob@jacob.remcomp.fr> - 2016-12-28 00:54 +0100
  Re: Pine 64 Noob <root@127.0.0.1> - 2016-12-28 11:27 +0100
    Re: Pine 64 jacobnavia <jacob@jacob.remcomp.fr> - 2016-12-28 12:10 +0100
      Re: Pine 64 Noob <root@127.0.0.1> - 2016-12-28 12:59 +0100
  Re: Pine 64 Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-12-28 10:10 -0800
    Re: Pine 64 supercat@casperkitty.com - 2016-12-29 08:30 -0800
    Re: Pine 64 David Brown <david.brown@hesbynett.no> - 2016-12-29 13:22 +0100
      Re: Pine 64 Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-12-29 07:47 -0800
        Re: Pine 64 Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-12-29 17:03 +0000
      Re: Pine 64 Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-12-29 04:50 -0800
        Re: Pine 64 Reinhardt Behm <rbehm@hushmail.com> - 2016-12-29 21:25 +0800
      Re: Pine 64 Keith Thompson <kst-u@mib.org> - 2016-12-29 09:28 -0800
      Re: Pine 64 Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-12-29 14:22 +0000
    Re: Pine 64 David Brown <david.brown@hesbynett.no> - 2016-12-29 13:28 +0100
    Re: Pine 64 Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-12-28 14:12 -0800
      Re: Pine 64 BartC <bc@freeuk.com> - 2016-12-28 22:23 +0000
      Re: Pine 64 Gareth Owen <gwowen@gmail.com> - 2016-12-29 18:43 +0000
    Re: Pine 64 David Brown <david.brown@hesbynett.no> - 2016-12-28 21:59 +0100
    Re: Pine 64 jacobnavia <jacob@jacob.remcomp.fr> - 2016-12-28 23:43 +0100
    Re: Pine 64 jt@toerring.de (Jens Thoms Toerring) - 2016-12-28 22:56 +0000
      Re: Pine 64 Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-12-28 16:00 -0800
        Re: A programming language called 'B64' Noob <root@127.0.0.1> - 2016-12-30 16:08 +0100

csiph-web