Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb: use std::vector instead of alloca in core_target::get_core_register_section
Date: Mon, 13 Jan 2020 03:30:00 -0000	[thread overview]
Message-ID: <CAPTJ0XEekeX_GAmjbFugZKsLyORiObTEeTxoL=Xj7DtEUW3A-A@mail.gmail.com> (raw)
In-Reply-To: <20200112201729.489317-1-simon.marchi@polymtl.ca>

On Sun, Jan 12, 2020, 15:17 Simon Marchi <simon.marchi@polymtl.ca> wrote:

> As I was trying to compile gdb for an m68k host, I got this error:
>
>   CXX    corelow.o
> In file included from /binutils-gdb/gdb/gdbsupport/common-defs.h:120,
>                  from /binutils-gdb/gdb/defs.h:28,
>                  from /binutils-gdb/gdb/corelow.c:20:
> /binutils-gdb/gdb/corelow.c: In member function 'void
> core_target::get_core_register_section(regcache*, const regset*, const
> char*, int, int, const char*, bool)':
> /binutils-gdb/gdb/../include/libiberty.h:727:36: error: 'alloca' bound is
> unknown [-Werror=alloca-larger-than=]
>   727 | # define alloca(x) __builtin_alloca(x)
>       |                    ~~~~~~~~~~~~~~~~^~~
> /binutils-gdb/gdb/corelow.c:625:23: note: in expansion of macro 'alloca'
>   625 |   contents = (char *) alloca (size);
>       |                       ^~~~~~
>
> We are using alloca to hold the contents of a the core register
> sections.  These sections are typically fairly small, but there is no
> realy guarantee, so I think it would be more reasonable to just use
> dynamic allocation here.
>

This seems to be in a common file, why did it only fail on m68k?


> gdb/ChangeLog:
>
>         * corelow.c (core_target::get_core_register_section): Use
>           std::vector instead of alloca.
> ---
>  gdb/corelow.c | 9 ++++-----
>  1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/gdb/corelow.c b/gdb/corelow.c
> index c53bf1df8fd8..e7efa652d62a 100644
> --- a/gdb/corelow.c
> +++ b/gdb/corelow.c
> @@ -594,7 +594,6 @@ core_target::get_core_register_section (struct
> regcache *regcache,
>  {
>    struct bfd_section *section;
>    bfd_size_type size;
> -  char *contents;
>    bool variable_size_section = (regset != NULL
>                                 && regset->flags & REGSET_VARIABLE_SIZE);
>
> @@ -622,8 +621,8 @@ core_target::get_core_register_section (struct
> regcache *regcache,
>                section_name.c_str ());
>      }
>
> -  contents = (char *) alloca (size);
> -  if (! bfd_get_section_contents (core_bfd, section, contents,
> +  std::vector<char> contents (size);
> +  if (! bfd_get_section_contents (core_bfd, section, contents.data (),
>

Since you're touching this, isn't usual style not to have a space after the
! ?

                                  (file_ptr) 0, size))
>      {
>        warning (_("Couldn't read %s registers from `%s' section in core
> file."),
> @@ -633,12 +632,12 @@ core_target::get_core_register_section (struct
> regcache *regcache,
>
>    if (regset != NULL)
>      {
> -      regset->supply_regset (regset, regcache, -1, contents, size);
> +      regset->supply_regset (regset, regcache, -1, contents.data (),
> size);
>        return;
>      }
>
>    gdb_assert (m_core_vec != nullptr);
> -  m_core_vec->core_read_registers (regcache, contents, size, which,
> +  m_core_vec->core_read_registers (regcache, contents.data (), size,
> which,
>                                    (CORE_ADDR) bfd_section_vma (section));
>  }
>
> --
> 2.24.1
>
>


  reply	other threads:[~2020-01-12 23:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-12 20:22 Simon Marchi
2020-01-13  3:30 ` Christian Biesinger via gdb-patches [this message]
2020-01-13  4:29   ` Simon Marchi
2020-01-13 10:45     ` Andreas Schwab
2020-01-13 17:03       ` Simon Marchi
2020-01-13 17:33 ` Tom Tromey
2020-01-13 19:36   ` Simon Marchi
2020-01-13 19:45 ` Pedro Alves
2020-01-13 20:20   ` Simon Marchi
2020-01-13 23:13     ` Pedro Alves
2020-01-13 23:21       ` Simon Marchi

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='CAPTJ0XEekeX_GAmjbFugZKsLyORiObTEeTxoL=Xj7DtEUW3A-A@mail.gmail.com' \
    --to=gdb-patches@sourceware.org \
    --cc=cbiesinger@google.com \
    --cc=simon.marchi@polymtl.ca \
    /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