From: Jim Blandy <jimb@red-bean.com>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Allow spaces in filenames to load command
Date: Wed, 07 Dec 2005 17:44:00 -0000 [thread overview]
Message-ID: <8f2776cb0512061504la4a7a5brada0edaeb051f0e4@mail.gmail.com> (raw)
In-Reply-To: <43956C93.5070709@st.com>
Okay, we have a bigger problem here than I'd thought.
generic_load is a generic implementation of the target to_load method,
for use by targets that just want to use target_write_memory_partial
to write the loadable sections of the exec file to the target's
memory. It's used by the GDB remote protocol and some of the other
remote targets. However:
- dve3900-rom.c, remote-m32r-sdi.c, remote-mips.c, and wince.c just
expect a filename.
- monitor.c uses sscanf ("%s 0x%lx") to parse its argument.
- remote-e7000.c parses -quiet and -nostart arguments, but no load offset.
- remote-sim.c passes it on to sim_load, which always seems to expect
a filename.
So testing for address equality is a way for generic_load to recognize
when it's being given a lone filename that shouldn't be broken up,
without changing load_command in a way that would break the seven
non-generic-load targets out there.
I feel morally compromised. :) Let me think about this a bit.
next prev parent reply other threads:[~2005-12-06 23:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 17:06 Andrew STUBBS
2005-12-06 18:23 ` Jim Blandy
2005-12-06 20:28 ` Andrew STUBBS
2005-12-07 17:44 ` Jim Blandy [this message]
2005-12-07 19:35 ` Jim Blandy
2005-12-07 23:25 ` Andrew STUBBS
2005-12-08 0:19 ` Andrew STUBBS
2006-02-20 17:07 ` Daniel Jacobowitz
2006-02-20 20:03 ` Jim Blandy
2006-02-20 20:38 ` Daniel Jacobowitz
2006-02-21 18:27 ` Andrew STUBBS
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=8f2776cb0512061504la4a7a5brada0edaeb051f0e4@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=andrew.stubbs@st.com \
--cc=gdb-patches@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