From: Herbert Poetzl <herbert@13thfloor.at>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Miguel Angel Flores <maf@sombragris.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel development environment
Date: Sun, 5 Dec 2004 21:16:52 +0100 [thread overview]
Message-ID: <20041205201652.GB1159@mail.13thfloor.at> (raw)
In-Reply-To: <1102268517.9242.16.camel@localhost.localdomain>
On Sun, Dec 05, 2004 at 05:41:59PM +0000, Alan Cox wrote:
> On Sad, 2004-12-04 at 17:52, Miguel Angel Flores wrote:
> > My actual development environment consists in a scratch vim editor,
> > diff, patch
> > and gcc. My question is: ¿What kind of tools use you, the kernel gurus, to
> > write and debug code? ¿It's enough with vi and gcc?
>
> Editor, compiler and at least two PC's, and occasionally gdbstubs
although I do not consider myself a 'kernel guru' ...
cscope and ctags will help with code navigation
QEMU and UML are good choices to do kernel testing
and if necessary debugging ...
HTH,
Herbert
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2004-12-05 20:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 17:52 Miguel Angel Flores
2004-12-04 17:56 ` Jan-Benedict Glaw
2004-12-04 20:21 ` Alessandro Amici
2004-12-04 20:52 ` Miguel Angel Flores
2004-12-04 21:37 ` Alessandro Amici
2004-12-04 21:47 ` Lee Revell
2004-12-04 21:40 ` Michal Schmidt
2004-12-04 22:45 ` Lee Revell
2004-12-04 23:37 ` Randy.Dunlap
2004-12-04 23:55 ` Lee Revell
2004-12-05 0:34 ` Michal Schmidt
2004-12-05 0:39 ` Lee Revell
2004-12-05 21:29 ` Baruch Even
2004-12-05 0:05 ` Jim Nelson
2004-12-16 1:35 ` Bill Davidsen
2004-12-04 21:58 ` Roger Luethi
2004-12-05 17:41 ` Alan Cox
2004-12-05 20:16 ` Herbert Poetzl [this message]
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=20041205201652.GB1159@mail.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=maf@sombragris.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
all inboxes | Powered by JetHome®