public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/7542] gdb.base/sim.exp
Date: Sun, 29 Mar 2015 22:06:00 -0000 [thread overview]
Message-ID: <bug-7542-4717-in1CdBfdx8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-7542-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=7542
--- Comment #1 from Mike Frysinger <vapier at gentoo dot org> ---
most sims have been converted to nrun now which provides unified command line
interfaces and callbacks. i'll update this bug when they've all been cut over.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-03-29 22:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-7542-4717@http.sourceware.org/bugzilla/>
2014-03-14 0:46 ` vapier at gentoo dot org
2015-03-29 22:06 ` vapier at gentoo dot org [this message]
2021-10-03 15:46 ` [Bug sim/7542] move all sims to common/nrun.c for unified CLI vapier at gentoo dot org
2021-10-31 17:24 ` [Bug sim/7542] sim: m32c rl78 rx: move " vapier at gentoo dot org
2021-10-31 17:25 ` vapier at gentoo dot org
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=bug-7542-4717-in1CdBfdx8@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).