Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@efficios.com>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: [PATCH 0/3] C++ification of symfile_segment_data
Date: Mon, 18 May 2020 21:35:30 -0400	[thread overview]
Message-ID: <20200519013533.1428830-1-simon.marchi@efficios.com> (raw)

As I was reading this code, I did this simple translation from manual
memory management to using C++ constructs.

Simon Marchi (3):
  gdb: allocate symfile_segment_data with new
  gdb: use std::vector to store segments in symfile_segment_data
  gdb: make symfile_segment_data::segment_info an std::vector

 gdb/elfread.c       | 17 ++++++-----------
 gdb/remote.c        | 22 ++++++++++------------
 gdb/solib-target.c  | 18 ++++++++----------
 gdb/symfile-debug.c |  2 +-
 gdb/symfile.c       | 45 ++++++++++++++-------------------------------
 gdb/symfile.h       | 41 +++++++++++++++++++++++------------------
 6 files changed, 62 insertions(+), 83 deletions(-)

-- 
2.26.2



             reply	other threads:[~2020-05-19  1:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19  1:35 Simon Marchi [this message]
2020-05-19  1:35 ` [PATCH 1/3] gdb: allocate symfile_segment_data with new Simon Marchi
2020-05-19  1:35 ` [PATCH 2/3] gdb: use std::vector to store segments in symfile_segment_data Simon Marchi
2020-05-19 14:55   ` Tom Tromey
2020-05-19 14:52     ` Simon Marchi
2020-05-19 15:44       ` Tom Tromey
2020-05-19  1:35 ` [PATCH 3/3] gdb: make symfile_segment_data::segment_info an std::vector Simon Marchi
2020-05-19 14:57 ` [PATCH 0/3] C++ification of symfile_segment_data Tom Tromey
2020-05-19 16:25   ` 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=20200519013533.1428830-1-simon.marchi@efficios.com \
    --to=simon.marchi@efficios.com \
    --cc=gdb-patches@sourceware.org \
    /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