public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/16442] New: sims not target-async
Date: Mon, 13 Jan 2014 15:23:00 -0000 [thread overview]
Message-ID: <bug-16442-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=16442
Bug ID: 16442
Summary: sims not target-async
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: sim
Assignee: unassigned at sourceware dot org
Reporter: tromey at redhat dot com
Currently the sims don't implement target-async, but they could.
There are three ways to do it.
The first way keeps the current restriction that only a single
sim can be used at a time. The idea is simple -- run the simulator
code in a separate thread, doing whatever locking is needed on
the gdb side. On the sim side this may need a bit of auditing
to make sure that the code is "thread safe enough"; plus some
minor changes to prevent the sims from installing their own
signal handlers.
The second way would also be to use multiple threads, but do more
auditing on the simulator code to (1) let multiple instances of
a given simulator run at once, and (2) let multiple simulators be
built and linked in (or dlopen'd) at the same time.
The third idea is to add a minimal RSP stub to the various drivers
(run.c, nrun.c, plus there is at least one custom one in tree) and
change "target sim" to be a wrapper around "target remote". Some
tricks -- perhaps threads again -- are needed here to make C-c work
properly; also this may break the sim command completion functionality.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-01-13 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 15:23 tromey at redhat dot com [this message]
2014-03-14 0:46 ` [Bug sim/16442] " vapier at gentoo dot org
2015-03-29 22:16 ` vapier at gentoo dot org
2022-11-29 16:22 ` tromey at sourceware dot org
2022-12-10 12:25 ` vapier at gentoo dot org
2023-06-13 17:21 ` mark at klomp 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-16442-4717@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).