From: "Amit S. Kale" <amitkale@emsyssoft.com>
To: George Anzinger <george@mvista.com>
Cc: Andrew Morton <akpm@osdl.org>,
jim.houston@comcast.net, discuss@x86-64.org, ak@suse.de,
shivaram.upadhyayula@wipro.com,
lkml <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>
Subject: Re: [discuss] Re: kgdb for x86_64 2.6 kernels
Date: Sat, 10 Jan 2004 16:11:53 +0530 [thread overview]
Message-ID: <200401101611.53510.amitkale@emsyssoft.com> (raw)
In-Reply-To: <3FFF2851.4060501@mvista.com>
George,
Well said!
I have released kgdb 2.0.1 for kernel 2.6.1:
http://kgdb.sourceforge.net/linux-2.6.1-kgdb-2.0.1.tar.bz2
It doesn't contain any assert stuff. I have split it into multiple parts to
make a merge easier. Please let me know if you want me to further split them
or if you want something to be changed. The README file from this tarball is
pasted below.
Here is two possible starting points:
1. SMP stuff -> Replace my old smp and nmi handling code.
2. Early boot -> Change 8250.patch to make configuration of serial port either
through config options or through command line.
I'll attempt reading your patch and merging as much stuff as possible.
Thanks.
Patch:
------
Patch the kernel out of following patches.
core.patch - KGDB architecture and interface independent code. Required.
i386.patch - i386 architecture dependent part. Required only for that
architecture.
x86_64.patch - x86_64 architecture dependent part. Required only for that
architecture.
8250.patch - Generic serial port (8250 and 16550) interface for kgdb. This
is the only working interface in this release. Hence required.
eth.patch - Ethernet interface for kgdb. This is still under development.
Use only if you plan to contribute to its development.
Build:
------
Enable following config options (in this order).
Kernel hacking ->
KGDB: kernel debugging with remote gdb ->
KGDB: Thread analysis
KGDB: Console messages through gdb
Device drivers ->
Character devices ->
Serial drivers ->
KGDB: On generic serial port (8250)
Boot:
-----
Supply command line options kgdbwait and kgdb8250 to the kernel.
Example: kgdbwait kgdb8250=1,115200
On Saturday 10 Jan 2004 3:46 am, George Anzinger wrote:
> Amit,
>
> The base line kgdb code in the mm patches was offered by me. It derives
> from (a long time ago) a kgdb I got from the RTIA (or was it the RTLINUX)
> folks. Prio to that, well, your name is on it as well as others.
>
> As you may have noted there have been a lot of changes, mostly for the
> better, I hope. I think we have slightly different objectives in our work.
> I debug kernels, not drivers, so I am interested in getting into kgdb as
> early as possible. To this end the current mm patch allows one to put a
> breakpoint() as the first line of C code in the kernel. This required a
> few adjustments, such as configuring the I/O port at CONFIG time, for
> example.
>
> I would like for the two versions of kgdb to merge while keeping the
> features of both. The work on seperating the common code is something I
> like and, while I never do modules, the automatic module stuff in gdb sound
> good.
>
> May I suggest that we compare and contrast the two versions and take a look
> at the differences and the overlaps and settle on one way of doing the
> various things.
>
> George
--
Amit Kale
EmSysSoft (http://www.emsyssoft.com)
KGDB: Linux Kernel Source Level Debugger (http://kgdb.sourceforge.net)
next prev parent reply other threads:[~2004-01-10 10:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000e01c3d476$2ebe03a0$4008720a@shivram.wipro.com>
[not found] ` <1073603622.993.353.camel@new.localdomain>
[not found] ` <20040108153243.11e45156.akpm@osdl.org>
[not found] ` <200401091031.41493.amitkale@emsyssoft.com>
2004-01-09 22:16 ` [discuss] Re: kgdb for x86_64 2.6 kernels George Anzinger
2004-01-10 10:41 ` Amit S. Kale [this message]
2004-01-10 15:03 ` Pavel Machek
2004-01-10 18:14 ` Pavel Machek
2004-01-12 14:32 ` Amit S. Kale
2004-01-10 19:30 ` Pavel Machek
2004-01-12 14:31 ` Amit S. Kale
2004-01-12 6:00 ` George Anzinger
2004-01-12 9:47 ` Pavel Machek
2004-01-13 20:55 ` George Anzinger
2004-01-12 14:50 ` Amit S. Kale
2004-01-13 21:26 ` George Anzinger
2004-01-14 6:31 ` Matt Mackall
2004-01-14 20:02 ` George Anzinger
2004-01-14 23:26 ` Greg KH
2004-01-15 0:02 ` George Anzinger
2004-01-15 0:19 ` Pavel Machek
2004-01-15 3:28 ` George Anzinger
2004-01-15 0:23 ` Greg KH
2004-01-15 3:30 ` George Anzinger
2004-01-14 13:24 ` Amit S. Kale
2004-01-14 22:32 ` George Anzinger
[not found] <1cd9t-4Su-65@gated-at.bofh.it>
[not found] ` <1coR2-42n-19@gated-at.bofh.it>
[not found] ` <1d3r0-1tw-3@gated-at.bofh.it>
[not found] ` <1dbI9-89t-7@gated-at.bofh.it>
[not found] ` <1dEqx-F0-1@gated-at.bofh.it>
[not found] ` <1dMRc-6DQ-3@gated-at.bofh.it>
[not found] ` <1e2Mk-6YA-17@gated-at.bofh.it>
[not found] ` <1e2Mo-6YA-31@gated-at.bofh.it>
[not found] ` <1e3fi-4nG-5@gated-at.bofh.it>
2004-01-15 8:02 ` Andi Kleen
2004-01-15 8:36 ` George Anzinger
2004-01-15 8:52 ` Andi Kleen
2004-01-16 1:15 ` Matt Mackall
2004-01-16 18:04 ` Randy.Dunlap
2004-01-16 21:07 ` Andi Kleen
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=200401101611.53510.amitkale@emsyssoft.com \
--to=amitkale@emsyssoft.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=george@mvista.com \
--cc=jim.houston@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=shivaram.upadhyayula@wipro.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