Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] MIPS16 FP manual call/return fixes
Date: Sat, 12 May 2012 19:38:00 -0000	[thread overview]
Message-ID: <20120512193750.GA26427@host2.jankratochvil.net> (raw)
In-Reply-To: <alpine.DEB.1.10.1205081109310.18334@tp.orcam.me.uk>

On Tue, 08 May 2012 16:29:44 +0200, Maciej W. Rozycki wrote:
>  I have decided to add a related_address field to bp_location; this could 
> get converted to an opaque member in the future in case some other 
> breakpoints need to carry other auxiliary information

[ Mostly unrelated to this patch:  ]

This should be C++ inherited class field; or in C it should be
bp_location-type driven union.

While I would find it cleaner with the union I do not request this as
mandatory for check-in, it could also start some new GDB coding style
discussions.


> (just as we do with some other structures).

[ Mostly unrelated to this patch:  ]

Unfortunately we do but we do not / no longer have to.


>  I have decided to keep the assertion you had concerns about after all.  

I meant that 'gdb_assert (is_gnu_ifunc);', that is gone now.


>  	      b->type = bp_gnu_ifunc_resolver;
[...]
> Is it ever possible for this breakpoint to be updated later on with
> additional locations?

I am not aware of.


> --- gdb-fsf-trunk-quilt.orig/gdb/elfread.c	2012-05-08 08:25:37.795639727 +0100
> +++ gdb-fsf-trunk-quilt/gdb/elfread.c	2012-05-08 09:42:32.075560588 +0100
> @@ -1020,21 +1020,15 @@ elf_gnu_ifunc_resolver_return_stop (stru
[...]
> +  CORE_ADDR func_func_addr;

This variable is unused now.


[...]
> --- gdb-fsf-trunk-quilt.orig/gdb/breakpoint.c	2012-05-04 19:26:24.845606346 +0100
> +++ gdb-fsf-trunk-quilt/gdb/breakpoint.c	2012-05-08 08:26:49.855603092 +0100
[...]
> @@ -6609,6 +6610,9 @@ set_breakpoint_location_function (struct
>  	      /* Create only the whole new breakpoint of this type but do not
>  		 mess more complicated breakpoints with multiple locations.  */
>  	      b->type = bp_gnu_ifunc_resolver;

Empty line before a comment according to GDB Coding Standards.

> +	      /* Remember the resolver's address for use by the return
> +	         breakpoint.  */
> +	      loc->related_address = func_addr;
>  	    }
>  	}
>  
[...]


OK for the IFUNC part from me.


Thanks,
Jan


  reply	other threads:[~2012-05-12 19:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23 13:30 Maciej W. Rozycki
2012-04-26 19:20 ` Tom Tromey
2012-04-26 22:23   ` Maciej W. Rozycki
2012-04-27 15:16     ` Maciej W. Rozycki
2012-04-27 15:28       ` Tom Tromey
2012-04-26 19:33 ` Tom Tromey
2012-04-30 23:45   ` Maciej W. Rozycki
2012-05-01 14:05     ` Jan Kratochvil
2012-05-01 17:22       ` Maciej W. Rozycki
2012-05-02 21:28         ` Jan Kratochvil
2012-05-08 14:30           ` Maciej W. Rozycki
2012-05-12 19:38             ` Jan Kratochvil [this message]
2012-05-14  9:12               ` Maciej W. Rozycki
2012-05-14 11:54                 ` Jan Kratochvil
2012-05-16 14:45                   ` Maciej W. Rozycki

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=20120512193750.GA26427@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@codesourcery.com \
    --cc=tromey@redhat.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