From: Werner Almesberger <wa@almesberger.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] kernel debugger for RH 7.3
Date: Mon, 07 Oct 2002 00:29:39 +0000 [thread overview]
Message-ID: <marc-lartc-103395063208894@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103394986808591@msgid-missing>
Daniel Sullivan wrote:
> I would like to step through the kernel and modules that perform traffic
> control.
Depending on what you plan to do, you may find tcsim a more convenient
tool than a kernel debugger. tcsim runs most of the traffic control
subsystem in user space, so you can just use gdb or any other debugger.
tcsim is part of tcng, http://tcng.sourceforge.net/
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-10-07 0:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 0:16 [LARTC] kernel debugger for RH 7.3 Daniel Sullivan
2002-10-07 0:29 ` Werner Almesberger [this message]
2002-10-08 15:11 ` EGAL Vincent
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=marc-lartc-103395063208894@msgid-missing \
--to=wa@almesberger.net \
--cc=lartc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.