From: matt@proweb.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fresh compiled kernels no longer boot..?
Date: Wed, 11 Feb 2004 23:30:02 +0000 [thread overview]
Message-ID: <40d45fe83ed048a7a6f757fad66dc33c@juice.thebigchoice.com> (raw)
In-Reply-To: <09e801c3e3a6$b9e9f620$67844051@SOMA>
> never underestimate the power of judiciously placed print[f]'s as a
> debugging tool.
but *please* remember to remove them before commiting ;)
and it would be wise to add a comment in case you don't fix the bug in this session but leave the printf
// printf for debugging the stderr problem
printf(2, "are you sure 2 is always stderr?\n");
m
next prev parent reply other threads:[~2004-02-11 23:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 22:05 Axel Belinfante
2004-01-25 22:37 ` David Presotto
2004-01-25 23:02 ` jmk
2004-01-25 23:12 ` Axel Belinfante
2004-01-25 23:43 ` Axel Belinfante
2004-01-25 23:52 ` jmk
2004-01-26 0:13 ` Axel Belinfante
2004-01-26 0:52 ` boyd, rounin
2004-02-11 23:30 ` matt [this message]
2004-02-12 2:54 ` boyd, rounin
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=40d45fe83ed048a7a6f757fad66dc33c@juice.thebigchoice.com \
--to=matt@proweb.co.uk \
--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).