Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Amit S. Kale" <amitkale@linsyssoft.com>
To: GDB discussions <gdb@sources.redhat.com>
Subject: kgdb support for gdb: patch 1
Date: Thu, 21 Oct 2004 17:22:00 -0000	[thread overview]
Message-ID: <200410211821.08680.amitkale@linsyssoft.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 475 bytes --]

Hi,

I have been working on the changes suggested by Mark K and Andrew C. Here is 
the first patch. This adds support for a new osabi for linux kernel.

I haven't added any support for detecting kernel osabi automatically. 
Detecting it with present kernel binary structure is rather shaky. It's safer 
to let users run the command "set osabi Linux-kernel".

I'll be later sending more patches.

Please review it and let me know if it's ok for inclusion in gdb.
Thanks.
-Amit

[-- Attachment #2: lk.patch --]
[-- Type: text/x-diff, Size: 2225 bytes --]

Index: gdb/gdb/i386-linux-tdep.c
===================================================================
--- gdb.orig/gdb/i386-linux-tdep.c	2004-08-07 02:28:28.000000000 +0530
+++ gdb/gdb/i386-linux-tdep.c	2004-10-21 18:18:18.000000000 +0530
@@ -27,6 +27,7 @@
 #include "inferior.h"
 #include "osabi.h"
 #include "reggroups.h"
+#include "elf-bfd.h"
 
 #include "gdb_string.h"
 
@@ -416,6 +417,26 @@
   set_gdbarch_skip_solib_resolver (gdbarch, glibc_skip_solib_resolver);
 }
 
+static void
+i386_linuxkernel_init_abi (struct gdbarch_info info, struct gdbarch *gdbarch)
+{
+  struct gdbarch_tdep *tdep = gdbarch_tdep (gdbarch);
+
+  /* Linux Kernel uses ELF format for vmlinux file.  */
+  i386_elf_init_abi (info, gdbarch);
+
+  set_gdbarch_num_regs (gdbarch, I386_LINUX_NUM_REGS);
+  set_gdbarch_register_name (gdbarch, i386_linux_register_name);
+  set_gdbarch_register_reggroup_p (gdbarch, i386_linux_register_reggroup_p);
+
+  tdep->gregset_reg_offset = i386_linux_gregset_reg_offset;
+  tdep->gregset_num_regs = ARRAY_SIZE (i386_linux_gregset_reg_offset);
+  tdep->sizeof_gregset = 17 * 4;
+
+  tdep->jb_pc_offset = 20;	/* From <bits/setjmp.h>.  */
+
+}
+
 /* Provide a prototype to silence -Wmissing-prototypes.  */
 extern void _initialize_i386_linux_tdep (void);
 
@@ -424,4 +445,6 @@
 {
   gdbarch_register_osabi (bfd_arch_i386, 0, GDB_OSABI_LINUX,
 			  i386_linux_init_abi);
+  gdbarch_register_osabi (bfd_arch_i386, 0, GDB_OSABI_LINUXKERNEL,
+			  i386_linuxkernel_init_abi);
 }
Index: gdb/gdb/defs.h
===================================================================
--- gdb.orig/gdb/defs.h	2004-10-12 15:36:14.000000000 +0530
+++ gdb/gdb/defs.h	2004-10-21 18:14:02.000000000 +0530
@@ -1031,6 +1031,7 @@
   GDB_OSABI_SOLARIS,
   GDB_OSABI_OSF1,
   GDB_OSABI_LINUX,
+  GDB_OSABI_LINUX_KERNEL,
   GDB_OSABI_FREEBSD_AOUT,
   GDB_OSABI_FREEBSD_ELF,
   GDB_OSABI_NETBSD_AOUT,
Index: gdb/gdb/osabi.c
===================================================================
--- gdb.orig/gdb/osabi.c	2004-07-03 02:57:17.000000000 +0530
+++ gdb/gdb/osabi.c	2004-10-21 18:14:02.000000000 +0530
@@ -57,6 +57,7 @@
   "Solaris",
   "OSF/1",
   "GNU/Linux",
+  "Linux-kernel",
   "FreeBSD a.out",
   "FreeBSD ELF",
   "NetBSD a.out",

             reply	other threads:[~2004-10-21 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-21 17:22 Amit S. Kale [this message]
2004-10-22 12:28 ` Mark Kettenis
2004-10-28 10:56   ` 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=200410211821.08680.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