Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Walfred Tedeschi <walfred.tedeschi@intel.com>, brobecker@adacore.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH V2 2/5] Preparation for new siginfo on Linux.
Date: Fri, 18 Dec 2015 12:39:00 -0000	[thread overview]
Message-ID: <5673FE78.5030900@redhat.com> (raw)
In-Reply-To: <1450371416-24270-2-git-send-email-walfred.tedeschi@intel.com>

On 12/17/2015 04:56 PM, Walfred Tedeschi wrote:
> First add new structure and function to allow architecture customization
> for the siginfo structure.
> 
> 2015-12-15  Walfred Tedeschi  <walfred.tedeschi@intel.com>
> 
> 	* linux-tdep.h (linux_siginfo_extra_field_values): New enum values.
> 	(linux_siginfo_extra_fields): New enum type.

	(linux_siginfo_extra_fields): New enum_flags type.


> 	* linux-tdep.c (linux_get_siginfo_type_with_fields): New function.
> 	(linux_get_siginfo_type): Uses new function.

	* linux-tdep.c (linux_get_siginfo_type): Rename to ...
        (linux_get_siginfo_type_with_fields): ... this.  Add parameter.
	(linux_get_siginfo_type): Reimplement as wrapper around
	linux_get_siginfo_type_with_fields.

> diff --git a/gdb/linux-tdep.h b/gdb/linux-tdep.h
> index 9beb6f6..c0c9d91 100644
> --- a/gdb/linux-tdep.h
> +++ b/gdb/linux-tdep.h
> @@ -24,6 +24,15 @@
>  

Should include common/enum-flags.h.  (And mention it in ChangeLog.)

>  struct regcache;
>  
> +/* Enum used to define which kind of siginfo is used by the architecture.  */

I'd suggest:

/* Flag values indicating the extra fields in an architecture's
   siginfo_t type.  */

> +enum linux_siginfo_extra_field_values
> +{
> +  LINUX_SIGINFO_FIELD_ADDR_BND = 1

Please document the value.


> +};
> +
> +/* Defines a type for the values defined in linux_siginfo_extra_field_values.  */

I think you can just say:

/* Define the corresponding enum_flags type.  */

> +DEF_ENUM_FLAGS_TYPE (enum linux_siginfo_extra_field_values, linux_siginfo_extra_fields);
> +
>  typedef char *(*linux_collect_thread_registers_ftype) (const struct regcache *,
>  						       ptid_t,
>  						       bfd *, char *, int *,


Thanks,
Pedro Alves


  reply	other threads:[~2015-12-18 12:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 16:57 [PATCH V2 1/5] Merges gdb and gdbserver implementation for siginfo Walfred Tedeschi
2015-12-17 16:57 ` [PATCH V2 4/5] Add bound related fields to the siginfo structure Walfred Tedeschi
2015-12-18 13:11   ` Pedro Alves
2015-12-17 16:57 ` [PATCH V2 5/5] Adapt siginfo fixup for the new bnd fields Walfred Tedeschi
2015-12-18 14:43   ` Pedro Alves
2015-12-18 14:53     ` Tedeschi, Walfred
2015-12-17 16:57 ` [PATCH V2 3/5] Use linux_get_siginfo_type_with_fields for x86 Walfred Tedeschi
2015-12-18 12:55   ` Pedro Alves
2015-12-17 16:57 ` [PATCH V2 2/5] Preparation for new siginfo on Linux Walfred Tedeschi
2015-12-18 12:39   ` Pedro Alves [this message]
2015-12-18 12:25 ` [PATCH V2 1/5] Merges gdb and gdbserver implementation for siginfo Pedro Alves

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=5673FE78.5030900@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=walfred.tedeschi@intel.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