From: Mark Kettenis <kettenis@gnu.org>
To: amitkale@linsyssoft.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: kgdb support for gdb
Date: Fri, 01 Oct 2004 22:01:00 -0000 [thread overview]
Message-ID: <200410012200.i91M0x8m001379@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <200410011314.33157.amitkale@linsyssoft.com>
From: "Amit S. Kale" <amitkale@linsyssoft.com>
Date: Fri, 1 Oct 2004 13:14:33 +0530
Hi,
Attached patches add kgdb support to gdb. They define two new
targets i386-lk and x86_64-lk. Because of the definition of these
targets, one can build a gdb with does not contain the linux
operating environment specific things which are inappropriate for
the kernel, like signal trampoline frame parsing.
I don't think you/we should add a new target triple for this stuff.
Instead you should add a special OS ABI variant for the kernel, and
use that to define your own kernel architecture vector. I suppose
there is a way to detect that a binary is a Linux kernel instead of a
normal ELF executable?
Oh, and if you want this code to be included in the official GDB
sources, you'll have to assign copyright to the FSF of course.
Mark
next prev parent reply other threads:[~2004-10-01 22:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 7:45 Amit S. Kale
2004-10-01 9:13 ` Andreas Schwab
2004-10-01 9:57 ` Amit S. Kale
2004-10-01 22:01 ` Mark Kettenis [this message]
2004-10-02 3:52 ` Amit S. Kale
2004-10-02 22:48 ` Mark Kettenis
2004-10-04 14:56 ` Andrew Cagney
2004-10-19 12:45 ` Amit S. Kale
2004-10-04 15:14 ` Andrew Cagney
2004-10-04 15:42 ` Amit S. Kale
2004-10-19 12:55 ` Amit S. Kale
2004-10-04 15:55 ` Andrew Cagney
2004-10-04 16:36 ` Amit S. Kale
2004-10-04 17:23 ` Daniel Jacobowitz
2004-10-25 5:50 ` Amit S. Kale
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=200410012200.i91M0x8m001379@elgar.sibelius.xs4all.nl \
--to=kettenis@gnu.org \
--cc=amitkale@linsyssoft.com \
--cc=gdb-patches@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