From: Keith Owens <kaos@melbourne.sgi.com>
To: Steve Kranz <skranz@ridgerun.com>
Cc: linux-mips@oss.sgi.com, linux-mips@fnet.fr
Subject: Re: remote GDB debugging and the __init macro of init.h
Date: Sat, 28 Oct 2000 12:54:18 +1100 [thread overview]
Message-ID: <4909.972698058@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Fri, 27 Oct 2000 09:24:17 MDT." <39F99E20.8EE47072@ridgerun.com>
On Fri, 27 Oct 2000 09:24:17 -0600,
Steve Kranz <skranz@ridgerun.com> wrote:
> I had to make a change to allow remote MIPS kernel
> debugging (GDB). The change I found necessary was in the
> file:
>
> include/linux/init.h (2.4.0-test9)
>
> As you can see from the snippet below the change
> involves conditionally defining the "__init" macro as
> a function of whether remote debugging is enabled or
> not. Am I missing something, or does this seem like a
> reasonable change?
It would be better to teach kgdb that the kernel has symbols in
sections other than .text. Even with your patch, you do not get all
the symbols, there is also code in sections .setup.init, .initcall.init
and .exitcall.exit, with similar sections for data. You cannot remove
.initcall.init without destroying the kernel initialization procedure.
Recent versions of kgdb for ix86 use a modified version of gdb that
knows about multiple sections for modules. I do not know if they have
the same functionality for the kernel.
prev parent reply other threads:[~2000-10-28 1:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 15:24 remote GDB debugging and the __init macro of init.h Steve Kranz
2000-10-27 15:50 ` Kevin D. Kissell
2000-10-27 15:50 ` Kevin D. Kissell
2000-10-28 1:53 ` Ralf Baechle
2000-10-30 17:53 ` Jun Sun
2000-10-31 4:12 ` Ralf Baechle
2000-10-28 1:54 ` Keith Owens [this message]
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=4909.972698058@ocs3.ocs-net \
--to=kaos@melbourne.sgi.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=skranz@ridgerun.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