From: Mike Frysinger <vapier@gentoo.org>
To: gdb@sourceware.org
Cc: Greg McGary <greg.mcgary@gmail.com>, Tom Tromey <tromey@redhat.com>
Subject: Re: gdb testsuite with remote target of qemu in linux-user mode?
Date: Tue, 14 Feb 2012 15:16:00 -0000 [thread overview]
Message-ID: <201202141015.54166.vapier@gentoo.org> (raw)
In-Reply-To: <4F3972F3.6030909@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1213 bytes --]
On Monday 13 February 2012 15:30:43 Greg McGary wrote:
> On 02/10/12 13:54, Tom Tromey wrote:
> > >>>>> "Greg" == Greg McGary <greg.mcgary@gmail.com> writes:
> > Greg> Does anyone use gdb testsuite with remote target of qemu in
> > Greg> linux-user mode? I see no mention of qemu as a remote simulator
> > Greg> in dejagnu, or in gdb/testsuite.
> >
> > Greg> I threw together a qemu.exp to do this, and it seems to work OK
> > Greg> everywhere except with mi-support.exp, which does not appear to
> > Greg> have infrastructure to spawn an external simulator.
> >
> > I haven't heard of anything, but I think it would be a welcome addition
> > to gdb/testsuite/boards, if you are so inclined.
>
> Correction: mi-support.exp can spawn sid, which is external. I think
> the sensible thing to do is take the sid.exp code and generalize it to
> become an external-sim framework, then write a small qemu.exp and
> new sid.exp to use it.
i'm not entirely clear on what you want to do. when you compile programs, you
want to run them through qemu-user to verify they execute properly ? or you
want to launch qemu-user in gdb mode and then have gdb connect to that remote
target ?
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-14 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 21:24 Greg McGary
2012-02-10 20:54 ` Tom Tromey
2012-02-13 20:31 ` Greg McGary
2012-02-14 15:16 ` Mike Frysinger [this message]
2012-02-14 15:23 ` Greg McGary
2012-02-14 17:24 ` Pedro Alves
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=201202141015.54166.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb@sourceware.org \
--cc=greg.mcgary@gmail.com \
--cc=tromey@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