From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31920 invoked by alias); 4 Jul 2008 10:58:26 -0000 Received: (qmail 31910 invoked by uid 22791); 4 Jul 2008 10:58:26 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 04 Jul 2008 10:58:09 +0000 Received: (qmail 30256 invoked from network); 4 Jul 2008 10:26:50 -0000 Received: from unknown (HELO orlando.local) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 4 Jul 2008 10:26:50 -0000 From: Pedro Alves To: Michael Snyder Subject: Re: Testing gdb/monitor.c Date: Fri, 04 Jul 2008 10:58:00 -0000 User-Agent: KMail/1.9.9 Cc: gdb-patches@sourceware.org References: <200807031459.29209.pedro@codesourcery.com> <1215111474.3549.47.camel@localhost.localdomain> In-Reply-To: <1215111474.3549.47.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807041158.05794.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-07/txt/msg00056.txt.bz2 Thanks Michael, On Thursday 03 July 2008 19:57:54, Michael Snyder wrote: > On Thu, 2008-07-03 at 14:59 +0100, Pedro Alves wrote: > > Guys, > > > > If I wanted to do some changes to the monitor target(s) (monitor.c), > > what's the best and easiest way to test them? I never used this > > target before. Do I need hardware for that, or is there > > some (maintaned) --target that uses it with a simulator? Or? > > Hmmm... > > The "monitor" target is for debugging a "bare metal" development > board that has no operating system, and doesn't even have a gdb > "stub" that can communicate using the remote protocol. > > It works by sending "rom monitor" type commands and interpreting > their output. > > Such a system is unlikely to implement threads. > I understand your desire to canonicalize target thread behavior, though. > > I don't know of any way to test the monitor target, except > by using real hardware that has a rom monitor for which gdb > has a syntax spec. > > It would certainly be possible to construct a gdbreplay-like > software emulation that would mimic a monitor target, but you > would still need a real one from which to record some sessions. > > The return on investment would probably be small, though... > ;-/ "probably"? :-) -- Pedro Alves