From: Uriel <uriell@binarydream.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] debugging p9p threads question
Date: Wed, 3 Aug 2005 08:20:08 +0100 [thread overview]
Message-ID: <20050803072008.GG9518@server4.lensbuddy.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0508021657400.27198@enigma.lanl.gov>
The most effective debugging tool is still careful thought, coupled with
judiciously placed print statements.
-- Brian W. Kernighan, in the paper Unix for Beginners (1979)
On Tue, Aug 02, 2005 at 05:00:18PM -0600, Ronald G. Minnich wrote:
>
>
> On Tue, 2 Aug 2005, Russ Cox wrote:
>
> > Print statements.
>
> interesting, that's the answer in the supercomputing world too.
>
> Geez, why are we spending all this money on debuggers :-)
>
> on the 65K CPU blue gene box, I've been told that "debugging with over 512
> CPUs is ... printf".
>
>
> > Your call to threadexitsall(0) at the end of
> > threadmain is wrong. It should be threadexits().
>
> Thanks. I did a stupid thing, changing the exits(0) from the plan 9
> version to this threadexitsall(0)! oops.
>
> ron
next prev parent reply other threads:[~2005-08-03 7:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 22:42 Ronald G. Minnich
2005-08-02 22:48 ` Russ Cox
2005-08-02 23:00 ` Ronald G. Minnich
2005-08-02 23:36 ` Charles Forsyth
2005-08-03 7:20 ` Uriel [this message]
2005-08-03 10:40 ` Russ Cox
2005-08-03 12:12 ` Ronald G. Minnich
2005-08-06 23:48 ` Harri Haataja
2005-08-09 14:48 ` Gorka guardiola
2005-08-03 0:12 YAMANASHI Takeshi
2005-08-03 0:31 ` Skip Tavakkolian
2005-08-03 5:49 ` LiteStar numnums
2005-08-03 6:56 ` Tim Newsham
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=20050803072008.GG9518@server4.lensbuddy.com \
--to=uriell@binarydream.org \
--cc=9fans@cse.psu.edu \
/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).