Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Nikos Balkanas <nikos.balkanas@eyeonix.com>
Cc: gdb@sourceware.org
Subject: Re: Kernel debugging
Date: Sat, 21 Dec 2013 09:28:00 -0000	[thread overview]
Message-ID: <201312210428.41834.vapier@gentoo.org> (raw)
In-Reply-To: <CAAdsYna0aE+Ky=SXZOWYGKDLmX7tu4ymg=DuXKn1GDRdAxTSeQ@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 971 bytes --]

On Saturday 21 December 2013 00:46:25 Nikos Balkanas wrote:
> Ty mike,

please don't top post in your replies

> 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 :-()?

are you confusing kdb and kgdb ?  kgdb is just a remote gdb stub.  you still 
need gdb running somewhere else to connect to it to do debugging.  which means 
you have full access to gdb's abilities.

note that QEMU also has a gdb stub in it.  so you could use one of its system 
binaries to boot a linux kernel and then connect your gdb client to it.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2013-12-21  9:28 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
2013-12-21  9:28     ` Mike Frysinger [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=201312210428.41834.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gdb@sourceware.org \
    --cc=nikos.balkanas@eyeonix.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