From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org,
"Frank Ch. Eigler" <fche@redhat.com>,
utrace-devel <utrace-devel@redhat.com>,
Roland McGrath <roland@redhat.com>,
Jim Keniston <jkenisto@us.ibm.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Subject: Re: [RFC] [PATCH] In-kernel gdbstub based on utrace Infrastructure.
Date: Mon, 30 Nov 2009 19:35:14 +0530 [thread overview]
Message-ID: <20091130140514.GD18879@linux.vnet.ibm.com> (raw)
In-Reply-To: <1259588232.20516.307.camel@laptop>
> >
> > I guess Christoph, Roland and Frank would be able to explain in a better
> > fashion the rational and advantages of this stub over convential gdb.
>
> Hmm,. wouldn't it make much more sense to extend the current kgdb stub
> to include userspace debugging, providing an all-in-one solution?
I see two limitations but I guess there could be ways to get over it.
1. gdb requiring file that needs to be debugged. I always
thought it can either be a user program or a vmlinux file. gdb makes
most of the information(i.e registers) from the remote protocol to
display the backtrace, variable values and the like by reading this
file.
2. Also I am not sure if gdb has a way to tell the remote to switch the
context and provide information(registers) pertaining to the user mode/
kernel mode.
There could be other limitations too that I may not be aware.
>
> I think it would be much more powerful to be able to observe the full
> software stack and not be limited by this user<->kernel barrier.
>
> (Provided the user has sufficient privileges of course).
In this implementation, the current user can debug his/her own
processes. May be if we can debug both the context from same gdb then we
might have to place restrictions..
--
Thanks and Regards
Srikar
>
next prev parent reply other threads:[~2009-11-30 14:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 12:03 [RFC] [PATCH] In-kernel gdbstub based on utrace Infrastructure Srikar Dronamraju
2009-11-30 12:09 ` Peter Zijlstra
2009-11-30 12:32 ` Srikar Dronamraju
2009-11-30 12:41 ` Peter Zijlstra
2009-11-30 13:19 ` Srikar Dronamraju
2009-11-30 13:37 ` Peter Zijlstra
2009-11-30 14:05 ` Srikar Dronamraju [this message]
2009-11-30 15:03 ` Frank Ch. Eigler
2009-11-30 15:11 ` Peter Zijlstra
2009-11-30 15:16 ` Ingo Molnar
2009-11-30 15:29 ` Frank Ch. Eigler
2009-12-01 16:11 ` Ingo Molnar
2009-12-01 17:00 ` Frank Ch. Eigler
2009-12-01 17:09 ` Ingo Molnar
2009-12-01 17:45 ` Frank Ch. Eigler
2009-12-01 21:15 ` Ingo Molnar
2009-12-08 21:58 ` Frank Ch. Eigler
2009-12-10 7:41 ` Ingo Molnar
2009-12-10 15:08 ` Frank Ch. Eigler
2009-12-10 18:16 ` Ingo Molnar
2009-12-11 1:27 ` Frank Ch. Eigler
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=20091130140514.GD18879@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=ananth@in.ibm.com \
--cc=fche@redhat.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=roland@redhat.com \
--cc=utrace-devel@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