From: newsham@lava.net (Tim Newsham)
Subject: [Unix-jun72] No luck with C compiler yet, but an idea
Date: Sun, 4 May 2008 15:56:57 -1000 (HST) [thread overview]
Message-ID: <Pine.BSI.4.64.0805041552440.20114@malasada.lava.net> (raw)
In-Reply-To: <20080505012356.GB67094@minnie.tuhs.org>
> I played around trying to get the last11c C compiler to work, but no luck
> yet. I can compile it using Apout and the existing cc, c0, c1, as binaries.
>
> Tim, I suspect that we need to modify the 0407 patch to also clear the
> bss area in core. Here are the headers from several binaries
The whole userland is zerod before the a.out is loaded. I did find
a bug -- I was setting u.break to text+data+bss when it should have
been core+text+data+bss - any dynamic allocation was probably giving
back incorrect pointers.
I committed the fix but I don't have a good way to test it. I can't
seem to enter a "}" character (or upper case lettes) into the console
so I cant easily type a test C program. Anyone know of a setting to
work around this or to translate ^M into ^J?
Anyway, if you have more problems, please send me a test program and
I'll try to debug it further.
> Warren
Tim Newsham
http://www.thenewsh.com/~newsham/
next prev parent reply other threads:[~2008-05-05 1:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 5:19 [Unix-jun72] init Tim Newsham
2008-05-04 5:31 ` Tim Newsham
2008-05-04 6:29 ` [TUHS] comparing s1 frags, s2 bits, 1ed and jun72 print out Tim Newsham
2008-05-04 20:18 ` [Unix-jun72] 0407 binaries on 1ed Tim Newsham
2008-05-04 22:33 ` Warren Toomey
2008-05-05 0:00 ` Tim Newsham
2008-05-05 1:17 ` [Unix-jun72] Another RK mount program Warren Toomey
2008-05-05 1:23 ` [Unix-jun72] No luck with C compiler yet, but an idea Warren Toomey
2008-05-05 1:56 ` Tim Newsham [this message]
2008-05-05 23:01 ` [Unix-jun72] uppercase input Warren Toomey
2008-05-04 6:50 ` [Unix-jun72] init Warren Toomey
2008-05-04 8:41 ` [Unix-jun72] Yes, a mount command Warren Toomey
2008-05-04 12:54 ` [Unix-jun72] init Brad Parker
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=Pine.BSI.4.64.0805041552440.20114@malasada.lava.net \
--to=newsham@lava.net \
/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).