From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: [BUG] MI: -target-download
Date: Wed, 21 Feb 2007 00:54:00 -0000 [thread overview]
Message-ID: <17883.25849.214098.881027@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20070220204320.GA19991@caradoc.them.org>
> This looks specific to the simulator. Take a look at
> sim/common/sim-load.c:
>
> if (verbose_p)
> {
> xprintf (callback, "Loading section %s, size 0x%lx %s ",
> bfd_get_section_name (result_bfd, s),
> (unsigned long) size,
> (lma_p ? "lma" : "vma"));
> xprintf_bfd_vma (callback, lma);
> xprintf (callback, "\n");
> }
>
> Whoops. It's got its own copy, it isn't using the GDB load routine at
> all.
OK, I see that I jumped to the wrong conclusion. I don't use it anyway but I
had thought it might be a simple fix to symfile.c. Might as well leave things
as they are.
Thanks.
--
Nick http://www.inet.net.nz/~nickrob
prev parent reply other threads:[~2007-02-20 21:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 20:22 Nick Roberts
2007-02-20 20:43 ` Daniel Jacobowitz
2007-02-20 21:15 ` Nick Roberts
2007-02-20 23:13 ` Daniel Jacobowitz
2007-02-21 0:54 ` Nick Roberts [this message]
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=17883.25849.214098.881027@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb@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