Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: bug-hurd@gnu.org, thomas@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [PATCH,Hurd] Fix deallocation after proc_getprocinfo call
Date: Sun, 23 Nov 2014 15:21:00 -0000	[thread overview]
Message-ID: <20141123152052.GG4576@type.youpi.perso.aquilenet.fr> (raw)
In-Reply-To: <20141123095629.GF5774@adacore.com>

Joel Brobecker, le Sun 23 Nov 2014 13:56:29 +0400, a écrit :
> The above does look unusual to me, but if it works and seems to be
> the only correct way, let's go with that.

It is a system interface actually, so we don't really have the choice :)

Samuel


  reply	other threads:[~2014-11-23 15:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-02 15:26 Samuel Thibault
2014-11-23  7:44 ` Joel Brobecker
2014-11-23  9:13   ` Samuel Thibault
2014-11-23  9:56     ` Joel Brobecker
2014-11-23 15:21       ` Samuel Thibault [this message]
2014-11-23 15:19   ` [PATCHv2,Hurd] " Samuel Thibault
2014-11-24  9:28     ` Joel Brobecker

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=20141123152052.GG4576@type.youpi.perso.aquilenet.fr \
    --to=samuel.thibault@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=bug-hurd@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=thomas@codesourcery.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