Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC 2/3] Record function descriptor address instead of function address in value
Date: Fri, 14 Oct 2016 17:35:00 -0000	[thread overview]
Message-ID: <1e73fccd01e8a226c95719bb334669d7@simark.ca> (raw)
In-Reply-To: <1476442387-17291-3-git-send-email-yao.qi@linaro.org>

On 2016-10-14 06:53, Yao Qi wrote:
> In this patch, I add a new gdbarch method convert_from_func_addr, which
> converts function address back to function descriptor address or
> function pointer address.  It is the reversed operation of
> convert_from_func_ptr_addr.  We convert function address to function
> descriptor address when,

I think these could be better named, byt saying what it converts from 
_and_ what it converts to.  With convert_from_func_addr, we know it 
takes as input a function address, but we don't know what it converts it 
to.  What about something like convert_func_address_to_descriptor (or 
convert_func_addr_to_desc if you prefer shorter names)?

I think that it would also be clearer if we always used the same 
terminology (address and descriptor seem good).  It is not very 
intuitive what is the difference between convert_from_func_ptr_addr and 
convert_from_func_addr.  "function pointer address" and "function 
address" sound too close to each other, so it's easy to confuse them...

> 3. User visible changes
> 
> This patch brings several user visible changes, which look more
> accurate, shown by this table below,
> 
>  COMMAND           BEFORE                       AFTER
>  p main            main function address        main function 
> descriptor
>                                                 address
>  disass main       disassembly function main    not changed
>  disass main+4,+4  disassembly 4 bytes from     disassembly 4 bytes 
> from
>                    function main address + 4    main's function 
> descriptor + 4
>  x/i main          show one instruction on      show one instruction on 
> main's
>                    function main address        function descriptor
> 
> Although the latter looks inconvenient, that is consistent to the
> meaning on C language level.  Due to these changes, test cases are
> adjusted accordingly.

Could you provide example of the actual output of those commands, before 
and after?  It is not clear to me what the difference will be.

Thanks,

Simon


  reply	other threads:[~2016-10-14 17:35 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 2/3] Record function descriptor address instead of function address in value Yao Qi
2016-10-14 17:35   ` Simon Marchi [this message]
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
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
2016-10-14 10:53 ` [RFC 3/3] Update " 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=1e73fccd01e8a226c95719bb334669d7@simark.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@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