From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: [compile] Relocate memcpy
Date: Wed, 24 Jan 2018 13:23:00 -0000 [thread overview]
Message-ID: <20180124132304.GA15685@host1.jankratochvil.net> (raw)
In-Reply-To: <868tcne98t.fsf@gmail.com>
On Wed, 24 Jan 2018 13:23:14 +0100, Yao Qi wrote:
> My understanding is some thing patches "bl memcpy" with the address told
> by gdb. I don't know the patching is done by libcc1 or something else.
gdb/compile/compile-object-load.c contains something like ld.so - it loads
object (.o) files and processes their relocations (rather bfd/ does that) to
copy them to mmap()ed areas. I was debugging it only on i686+x86_64.
Jan
prev parent reply other threads:[~2018-01-24 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 12:23 Yao Qi
2018-01-24 13:23 ` Jan Kratochvil [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=20180124132304.GA15685@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=qiyaoltc@gmail.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