From: "Amit S. Kale" <amitkale@linsyssoft.com>
To: GDB discussions <gdb@sources.redhat.com>
Subject: Fwd: New gdb targets i386-lk and x86_64-lk
Date: Mon, 20 Sep 2004 10:20:00 -0000 [thread overview]
Message-ID: <200409201549.45628.amitkale@linsyssoft.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 131 bytes --]
FYI.
I'll be submitting these patches when at least some of the items in the
wishlist are done and the patches are stable.
-Amit
[-- Attachment #2: "Amit S. Kale" <amitkale@linsyssoft.com>: New gdb targets i386-lk and x86_64-lk --]
[-- Type: message/rfc822, Size: 1883 bytes --]
From: "Amit S. Kale" <amitkale@linsyssoft.com>
To: KGDB bugreports <kgdb-bugreport@lists.sourceforge.net>
Subject: New gdb targets i386-lk and x86_64-lk
Date: Mon, 20 Sep 2004 15:43:28 +0530
Message-ID: <200409201543.28855.amitkale@linsyssoft.com>
Hi,
I have created a new directory "gdb" in the cvs tree. This directory will
contain gdb patches similar to the directory "kgdb-2". Currently there is
only one patch lk.patch This patch adds two targets i386-lk and x86_64-lk.
The targets i386-lk and x86_64-lk are similar to i386-linux and x86_64-linux
respectively, though they contain different target dependent files. Creating
new targets will help us implement kgdb support for gdb in a better way
without the clutter of user level stuff.
Present patch is only a starter, so it doesn't contain all the things that are
present in gdbmod as yet. Here is my wishlist of things to be added:
1. Module scanning - Since we are free from solib.c now, we can implement a
fast module scanning algorithm.
2. Backtraces - Signal trampoline parsing is absent in this target, so gdb
won't get confused because signal trampoline handling code. We can make the
kernel backtraces stop at system calls, interrupt and exception handling
functions correctly. We should also be able to handle switching from regular
stack to interrupt-exception stack on x86_64 in gdb code itself.
3. Reading of /proc/kcore - kcore is already supported by gdb as it is. gdb
can't scan the list of kernel threads or modules loaded in a kernel. This
support can be added.
-Amit
reply other threads:[~2004-09-20 10:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200409201549.45628.amitkale@linsyssoft.com \
--to=amitkale@linsyssoft.com \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).