From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] PDP-8 (was: 2.11BSD cross compiler)
Date: Sat, 2 Oct 2010 13:46:01 +1000 [thread overview]
Message-ID: <20101002034601.GE66070@dereel.lemis.com> (raw)
In-Reply-To: <20100930135029.GB30928@bitmover.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1818 bytes --]
On Thursday, 30 September 2010 at 6:50:29 -0700, Larry McVoy wrote:
>>>> If you don't get the question you are not an OS person,
>>>> if you are, of course you get it.
>>
>> Hmm. Am I expected to understand this? Seriously, I don't know how
>> many people really wrote anything like swtch ().
>
> You'd be amazed at how many people did their own user level threads.
> Gotta write swtch() for that.
I think you're missing the joke. But swtch () is a specific kernel
function in UNIX, though in this thread (excuse the pun) people seem
to be using it as a synonym for a scheduler. And not many people need
to write their threading library by hand any more.
> And it's not swtch() so much as do you understand the stack frames?
That's a different issue. Any programmer worth his salt needs to
understand the underlying hardware, including stack frames. For my
personal understanding of them, see
http://www.lemis.com/grog/Documentation/PUS/porting_unix_software/obj.pdf
towards the end, or http://www.lemis.com/grog/Papers/Debug-tutorial/
for the kernel context, page 17 on.
> If you could look at the stack frames and give me a stack trace
> that's more or less the same thing.
(gdb) bt
The real question is not to get a stack trace, but to analyse it.
Greg
--
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. See
http://www.lemis.com/grog/email/signed-mail.php for more details.
If your Microsoft MUA reports problems, please read
http://tinyurl.com/broken-mua
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20101002/e02ab2c7/attachment.sig>
next prev parent reply other threads:[~2010-10-02 3:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 5:54 [TUHS] 2.11BSD cross compiler Nick Downing
2010-09-29 0:24 ` Tim Newsham
2010-09-29 0:51 ` Larry McVoy
2010-09-29 2:14 ` John Cowan
2010-09-29 2:38 ` Larry McVoy
2010-09-29 2:59 ` John Cowan
2010-09-29 3:44 ` Larry McVoy
2010-09-30 4:22 ` [TUHS] PDP-8 (was: 2.11BSD cross compiler) Greg 'groggy' Lehey
2010-09-30 4:53 ` John Cowan
2010-09-30 13:50 ` Larry McVoy
2010-10-02 3:46 ` Greg 'groggy' Lehey [this message]
2010-10-02 21:03 ` Larry McVoy
2010-10-02 21:39 ` [TUHS] PDP-8 M. Warner Losh
2010-10-02 10:06 ` [TUHS] PDP-8 (was: 2.11BSD cross compiler) Wolfgang Helbig
2010-09-29 3:14 ` [TUHS] 2.11BSD cross compiler M. Warner Losh
2010-09-29 3:17 ` Steve Nickolas
2010-09-29 3:55 ` Larry McVoy
2010-09-29 4:34 ` [TUHS] 6502 and swtch, was " Warren Toomey
2010-09-29 5:13 ` Steve Nickolas
2010-09-30 17:49 ` Tim Newsham
2010-09-29 20:54 ` [TUHS] " Peter Jeremy
2010-09-29 21:34 ` Larry McVoy
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=20101002034601.GE66070@dereel.lemis.com \
--to=grog@lemis.com \
/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).