From: Andrew Cagney <ac131313@ges.redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
jorma.laaksonen@hut.fi, gdb-gnats@sources.redhat.com,
gdb@sources.redhat.com
Subject: Re: gdb/633: fully qualified pathnames in solib_map_sections() and remote debugging
Date: Mon, 12 Aug 2002 09:20:00 -0000 [thread overview]
Message-ID: <3D57E028.8030809@ges.redhat.com> (raw)
In-Reply-To: <1020812154849.ZM31876@localhost.localdomain>
> At the moment, I like the first approach better because it's simpler.
> I'd prefer that we wait on the more complicated approach until a need
> is demonstrated for the additional complexity.
>
>
>> Adding a local/remote test is going to be easier.
>
>
> Do we already have such a test?
Well, looking at some finally dead hacks, ....
int
remote_Z_write_wp_packet_supported_p (void)
{
struct remote_state *rs = get_remote_state ();
/* Don't even think about it if the remote target isn't selected. */
/* FIXME: cagney/2002-05-19: This shouldn't be necessary - the
WATCHPOINT methods should be in the target vector. Ulgh! */
if (target_shortname == NULL
|| strcmp (target_shortname, "remote") != 0)
return 0;
notice that the problem it was trying to avoid was with ``target sim''.
So in the above the question is no longer local/remote but local VS
remote VS sim VS ....
Andrew
next prev parent reply other threads:[~2002-08-12 16:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020806100634.11483.qmail@sources.redhat.com>
2002-08-06 6:20 ` Daniel Jacobowitz
2002-08-09 16:12 ` Kevin Buettner
2002-08-11 20:25 ` Daniel Jacobowitz
2002-08-12 4:18 ` Jorma Laaksonen
2002-08-12 7:28 ` Andrew Cagney
2002-08-12 7:37 ` Daniel Jacobowitz
2002-08-12 8:07 ` Andrew Cagney
2002-08-12 8:48 ` Kevin Buettner
2002-08-12 8:55 ` Daniel Jacobowitz
2002-08-12 9:20 ` Kevin Buettner
2002-08-12 9:29 ` Daniel Jacobowitz
2002-08-12 9:20 ` Andrew Cagney [this message]
2002-08-12 9:31 ` Daniel Jacobowitz
2002-08-12 9:40 ` Kevin Buettner
2002-08-12 9:53 ` GDB functionalities for debugging Elf core dump Lucy Zhang
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=3D57E028.8030809@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=drow@mvista.com \
--cc=gdb-gnats@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jorma.laaksonen@hut.fi \
--cc=kevinb@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