Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Caz Yokoyama <cazyokoyama@gmail.com>
To: <jan.kiszka@web.de>
Cc: <gdb@sourceware.org>
Subject: RE: symbolic debug of loadable modules with kgdb light
Date: Fri, 09 Jan 2009 11:28:00 -0000	[thread overview]
Message-ID: <C061EF05AAC947979BBCCAE221D06834@xpjpn> (raw)
In-Reply-To: <496730C3.1000302@web.de>

Hello,
Did you happen to try the former extension with the QEMU or KVM backend
already? 
---
No. I am glad if you tell me how to do that. I saw a paper which talked
about running kgdb for guest OS of Xen.
(http://www.kernel.org/doc/ols/2006/ols2006v2-pages-9-24.pdf). I know there
is serial console in Virtual Machine Manager, i.e. select Guest OS ->
Details -> view -> serial console. But I have no idea how to connect it.

Is it possible to disable the SysRq interrupt for this use case?
----
I am not clear your point. My modification uses SysRq. I mean there are two
ways to generate SysRq, 1) from keyboard and 2) from serial port. 1) is
obvious, i.e. hit Ctrl+Alt+SysRq + g. 2) is BREAK and g. When my modified
gdb is invoked, it sends BREAK and g which break-in to kernel. Did I answer
your question? Or are you asking something else?
-caz

-----Original Message-----
From: jan.kiszka@web.de [mailto:jan.kiszka@web.de] 
Sent: Friday, January 09, 2009 3:11 AM
To: Caz Yokoyama
Cc: gdb@sourceware.org
Subject: Re: symbolic debug of loadable modules with kgdb light

Caz Yokoyama wrote:
> Hello,
> I started a sourceforge project called kgdb-light
> (http://sourceforge.net/projects/kgdb-light/). kgdb-light is a modified
gdb
> which handles symbol tables of loadable modules of Linux kernel 2.6.26 and
> later. Linux kernel 2.6.26 and later integrates kernel debugging under
> kernel hacking. Gdb handles symbol table of Linux kernel, but it does not
> for loadable modules. Kgdb-light updates internal symbol table by reading
> "struct module" in kernel. I also modified gdb to send Magic SysRq,
> therefore, target may locate far away.
> 

Sounds very interesting. Did you happend to try the former extension
with the QEMU or KVM backend already? Would be _very_ cool if such
support became mainline (I'm tired of add-symbol-file with manually
looked-up module addresses...). Is it possible to disable the SysRq
interrupt for this use case? [ I still consider this variation of the
original remote protocol an unfortunate decision of the kernel
developers, but back then I wasn't able to convince them to change it. ]

Jan



  reply	other threads:[~2009-01-09 11:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 14:09 Caz Yokoyama
2009-01-08 19:04 ` Tiago Maluta
2009-01-08 19:40   ` Caz Yokoyama
2009-01-08 19:42   ` Caz Yokoyama
2009-01-09  4:18 ` Joel Brobecker
2009-01-09 14:52   ` Caz Yokoyama
2009-01-09 18:17     ` Joel Brobecker
2009-01-09 19:33       ` Caz Yokoyama
2009-01-10  6:40       ` Daniel Jacobowitz
     [not found]       ` <B28296C4454C4B539564033161523A12@xpjpn>
2009-01-11  3:38         ` Joel Brobecker
2009-01-09 11:11 ` Jan Kiszka
2009-01-09 11:28   ` Caz Yokoyama [this message]
2009-01-09 12:38     ` Jan Kiszka
2009-01-09 16:29       ` Caz Yokoyama

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=C061EF05AAC947979BBCCAE221D06834@xpjpn \
    --to=cazyokoyama@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=jan.kiszka@web.de \
    /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