Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] gdb lwp_info: Add destructor, initialize fields, use new/delete
Date: Mon, 24 Jul 2017 10:43:00 -0000	[thread overview]
Message-ID: <8921fa5c7c80f9ec0f46b98781fd56f4@polymtl.ca> (raw)
In-Reply-To: <1500892797-7523-2-git-send-email-simon.marchi@ericsson.com>

On 2017-07-24 12:39, Simon Marchi wrote:
> From: Simon Marchi <simon.marchi@polymtl.ca>
> 
> Partially convert the lwp_info type to C++ by adding a constructor and
> initializing fields directly in the struct declaration.  Also, change a
> few fields to bool.
> 
> I did this patch in order to be able to use a unique_ptr field in a
> following patch.

Err, the title should say "constructor", not "destructor".  Fixed it 
locally.


  reply	other threads:[~2017-07-24 10:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 10:40 [PATCH 0/3] Create arch_lwp_info class hierarchy Simon Marchi
2017-07-24 10:40 ` [PATCH 2/3] gdbserver lwp_info: Initialize fields, use new/delete Simon Marchi
2017-07-25  9:58   ` Yao Qi
2017-07-25 10:19     ` Simon Marchi
2017-07-25 15:25       ` Yao Qi
2017-07-24 10:40 ` [PATCH 1/3] gdb lwp_info: Add destructor, initialize " Simon Marchi
2017-07-24 10:43   ` Simon Marchi [this message]
2017-07-25  9:39   ` Yao Qi
2017-07-24 10:40 ` [PATCH 3/3] Create arch_lwp_info class hierarchy Simon Marchi
2017-08-09 20:47   ` Simon Marchi
2017-08-11 20:13 ` [PATCH 0/3] " Pedro Alves
2017-08-12 11:31   ` Simon Marchi
2017-08-14 11:53     ` Pedro Alves
2017-08-16 18:44       ` Simon Marchi
2017-08-18 11:23         ` 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=8921fa5c7c80f9ec0f46b98781fd56f4@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.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