From: Yao Qi <qiyaoltc@gmail.com>
To: "Maciej W. Rozycki" <macro@imgtec.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC 2/3] Record function descriptor address instead of function address in value
Date: Tue, 18 Oct 2016 13:03:00 -0000 [thread overview]
Message-ID: <CAH=s-PNGxONkOse+qi=UemM=YCCjBXZ8QsGPXUpdWy9DfDX57w@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1610180255070.31859@tp.orcam.me.uk>
On Tue, Oct 18, 2016 at 3:27 AM, Maciej W. Rozycki <macro@imgtec.com> wrote:
>
> What about `info address main'?
>
It is unchanged. It shows the function address of main,
(gdb) info address main
Symbol "main" is a function at address 0x1000073c.
(gdb) disassemble main
Dump of assembler code for function main:
0x000000001000073c <+0>: mflr r0
I'll respond to the rest of your mail later, after I got some clues/ideas for
both your and Ulrich's comments.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-10-18 13:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 10:53 [PATCH 0/3] Fix gdb.base/func-ptrs.exp fails in ppc64 and arm thumb mode Yao Qi
2016-10-14 10:53 ` [RFC 3/3] Update test cases Yao Qi
2016-10-14 10:53 ` [RFC 2/3] Record function descriptor address instead of function address in value Yao Qi
2016-10-14 17:35 ` Simon Marchi
2016-10-17 11:40 ` Yao Qi
2016-10-17 15:40 ` Simon Marchi
2016-10-17 15:51 ` Ulrich Weigand
2016-10-18 2:27 ` Maciej W. Rozycki
2016-10-18 13:03 ` Yao Qi [this message]
2016-10-28 16:20 ` Yao Qi
2017-10-03 18:12 ` Maciej W. Rozycki
2017-10-04 21:25 ` Yao Qi
2016-10-28 16:10 ` Yao Qi
2016-10-28 18:41 ` Ulrich Weigand
2016-10-14 10:53 ` [PATCH 1/3] Use get_var_address in test cases 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='CAH=s-PNGxONkOse+qi=UemM=YCCjBXZ8QsGPXUpdWy9DfDX57w@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@imgtec.com \
--cc=uweigand@de.ibm.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