From: Vladimir Prus <vladimir@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Make sure target supports non-stop.
Date: Fri, 15 Aug 2008 17:02:00 -0000 [thread overview]
Message-ID: <200808152101.51407.vladimir@codesourcery.com> (raw)
In-Reply-To: <u7iaife8v.fsf@gnu.org>
On Friday 15 August 2008 20:13:20 Eli Zaretskii wrote:
> > From: Vladimir Prus <vladimir@codesourcery.com>
> > Date: Fri, 15 Aug 2008 18:50:47 +0400
> >
> > + if (non_stop && !target_supports_non_stop ())
> > + error (_("Cannot attach to this target in non-stop mode"));
>
> Won't it be more elegant to define a method enter_non_stop_mode for
> each target, and have the target complain if it cannot?
I'm not sure it will be better. Non-stop mode is not purely a property
of target, encapsulated inside it. Rather, it's global property, which
must be supported by target, so enabling it in core, after making sure
that target is fine with that, seems reasonable. In other words,
'enter_non_stop_mode' target method cannot do much except for emitting
an error if non stop is not supported, therefore a method which just reports
support for non-stop seems exactly right choice.
- Volodya
next prev parent reply other threads:[~2008-08-15 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 14:51 Vladimir Prus
2008-08-15 16:14 ` Eli Zaretskii
2008-08-15 17:02 ` Vladimir Prus [this message]
2008-08-15 17:45 ` Daniel Jacobowitz
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=200808152101.51407.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.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