From: Nikos Balkanas <nikos.balkanas@eyeonix.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb@sourceware.org
Subject: Re: Kernel debugging
Date: Sat, 21 Dec 2013 05:46:00 -0000 [thread overview]
Message-ID: <CAAdsYna0aE+Ky=SXZOWYGKDLmX7tu4ymg=DuXKn1GDRdAxTSeQ@mail.gmail.com> (raw)
In-Reply-To: <201312201441.24149.vapier@gentoo.org>
Ty mike,
I am aware of kdgb, but it doesn't have gdb's abilities. Besides I
know extensibly gdb, and I can never find the Sysreq key on my
keyboard :-(. I will try it next time, but for now I solved my problem
by reading the kernel source code. I have noticed the remote_vis.c in
gdb sources. Does this mean I can use gdb remotely to a virtual host?
How can i do it? Furthermore have gdbstubs incorporated into gdb
sources, or is it another abandoned project (since 2003 :-()?
Nikos
On Fri, Dec 20, 2013 at 9:41 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Thursday 19 December 2013 13:51:36 Nikos Balkanas wrote:
>> I am developing a module for the Linux kernel. For that i have setup
>> the exact environment in Virtual Box and have loaded the (guest)
>> kernel with -g and removed the -frame-pointers. I will run gdb from
>> host and try to debug kernel on guest system.
>>
>> What is the best approach for this scenario? GDBserver or gdbstubs?.
>> Gdb server is good only for userspace debugging. Will gdbstubs work?
>> Are they included in the recent gdb sources, or are the ones to use
>> since 2003 from sourceforge? I am also looking for instructions on how
>> to implement them. Any hints?
>
> the kernel has a built in gdb stub. look for "kgdb" in the
> documentation/kconfig.
> -mike
next prev parent reply other threads:[~2013-12-21 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 18:51 Nikos Balkanas
2013-12-20 19:41 ` Mike Frysinger
2013-12-21 5:46 ` Nikos Balkanas [this message]
2013-12-21 9:28 ` Mike Frysinger
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='CAAdsYna0aE+Ky=SXZOWYGKDLmX7tu4ymg=DuXKn1GDRdAxTSeQ@mail.gmail.com' \
--to=nikos.balkanas@eyeonix.com \
--cc=gdb@sourceware.org \
--cc=vapier@gentoo.org \
/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