From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1JvXVG-0003FN-Ve
	for qemu-devel@nongnu.org; Mon, 12 May 2008 08:51:43 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1JvXVF-0003Eg-A2
	for qemu-devel@nongnu.org; Mon, 12 May 2008 08:51:42 -0400
Received: from [199.232.76.173] (port=44117 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1JvXVE-0003ET-VO
	for qemu-devel@nongnu.org; Mon, 12 May 2008 08:51:41 -0400
Received: from nan.false.org ([208.75.86.248]:54129)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <drow@false.org>) id 1JvXVE-0006gf-FE
	for qemu-devel@nongnu.org; Mon, 12 May 2008 08:51:40 -0400
Date: Mon, 12 May 2008 08:51:35 -0400
From: Daniel Jacobowitz <drow@false.org>
Subject: Re: [Qemu-devel] Debugging vmlinux with qemu and gdb. Unable to
	step, next, print or to get any information..
Message-ID: <20080512125135.GA30870@caradoc.them.org>
References: <824D057211107844BA95DB341B4BF12E01139BF2@hanvsmail04.eu.thmulti.com>
	<f284c33d0805081931u72ca5b3fr80bf4c9b1721bc37@mail.gmail.com>
	<4823D56F.1010600@windriver.com>
	<20080509144029.GA32414@caradoc.them.org>
	<20080512094103.GA31632@edgar.se.axis.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080512094103.GA31632@edgar.se.axis.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Edgar E. Iglesias" <edgar.iglesias@axis.com>
Cc: qemu-devel@nongnu.org

On Mon, May 12, 2008 at 11:41:03AM +0200, Edgar E. Iglesias wrote:
> Thanks for the comments Daniel.
> 
> This patch tries to change the syntax into this:
> % monitor sstepbits
> % monitor sstep
> % monitor sstep=0x05
> 
> Or would a show/set interface be prefered for some reason (e.g,
> monitor show sstepbits, monitor show sstep, monitor set sstep 0x5)?

The only reason I suggested set/show is that that's how the GDB
command line works.  I think the important part is using monitor
rather than custom packets; the set style is just sugar.

Thanks!

-- 
Daniel Jacobowitz
CodeSourcery