From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patchv4 4/5] Keep objfile original filename
Date: Tue, 07 Jan 2014 18:47:00 -0000 [thread overview]
Message-ID: <20140107184716.GA12455@host2.jankratochvil.net> (raw)
In-Reply-To: <52CC02B1.9060607@codesourcery.com>
On Tue, 07 Jan 2014 14:35:45 +0100, Yao Qi wrote:
> We add an argument name here, but don't update
> spu_symbol_file_add_from_memory in spu-linux-nat.c. We get a build
> error below, when we build GDB with --target=spu-elf on powerpc-linux
> machine.
Sorry I did not build GDB on all archs; despite I have ppc accessible.
> This patch fixes the build error, but I am not sure NAME we passed to
> symbol_file_add_from_bfd is desired. IIUC, the NAME is "<in-memory>".
> I didn't run testsuite. Is it OK?
Yes, it is OK. The parameter is there for a difference for real disk files
between their original name with symlinks vs. their realpath() name.
Thanks,
Jan
> --- a/gdb/spu-linux-nat.c
> +++ b/gdb/spu-linux-nat.c
> @@ -379,7 +379,8 @@ spu_symbol_file_add_from_memory (int inferior_fd)
> {
> struct cleanup *cleanup = make_cleanup_bfd_unref (nbfd);
>
> - symbol_file_add_from_bfd (nbfd, SYMFILE_VERBOSE | SYMFILE_MAINLINE,
> + symbol_file_add_from_bfd (nbfd, bfd_get_filename (nbfd),
> + SYMFILE_VERBOSE | SYMFILE_MAINLINE,
> NULL, 0, NULL);
> do_cleanups (cleanup);
> }
> --
> 1.7.7.6
next prev parent reply other threads:[~2014-01-07 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 14:20 Jan Kratochvil
2013-09-19 23:37 ` Doug Evans
2013-09-24 14:01 ` [commit] " Jan Kratochvil
2014-01-07 13:37 ` Yao Qi
2014-01-07 18:47 ` Jan Kratochvil [this message]
2014-01-08 2:47 ` Yao Qi
2014-01-08 3:23 ` Tom Tromey
2014-01-08 6:26 ` Yao Qi
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=20140107184716.GA12455@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).