Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>,
	       Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: "'GDB Patches'" <gdb-patches@sourceware.org>
Subject: Re: Build failure following: Implement support for checking /proc/PID/coredump_filter commit
Date: Wed, 08 Apr 2015 17:21:00 -0000	[thread overview]
Message-ID: <552563A2.6050409@redhat.com> (raw)
In-Reply-To: <87a8yi1sar.fsf@redhat.com>

On 04/08/2015 05:46 PM, Sergio Durigan Junior wrote:
>> >   I have no idea what we should do now...
> IMO the easiest and safest thing to do now would be to just import the
> strtok_r module from gnulib (without updating it).

Yeah.  I posted the branch as proper patch series now.

 https://sourceware.org/ml/gdb-patches/2015-04/msg00288.html

Thanks,
Pedro Alves


  reply	other threads:[~2015-04-08 17:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 23:57 [PATCH v4 0/2] Improve corefile generation by using /proc/PID/coredump_filter (PR corefile/16902) Sergio Durigan Junior
2015-03-24 23:57 ` [PATCH 2/2] Documentation and testcase Sergio Durigan Junior
2015-03-27  9:53   ` Pedro Alves
2015-03-24 23:57 ` [PATCH 1/2] Implement support for checking /proc/PID/coredump_filter Sergio Durigan Junior
2015-03-27  9:53   ` Pedro Alves
2015-03-31 23:40     ` Sergio Durigan Junior
2015-04-08 14:08       ` Build failure following: Implement support for checking /proc/PID/coredump_filter commit Pierre Muller
2015-04-08 14:43         ` Pedro Alves
2015-04-08 15:14           ` Pedro Alves
2015-04-08 16:08             ` Sergio Durigan Junior
2015-04-08 16:28             ` Pierre Muller
2015-04-08 16:47               ` Sergio Durigan Junior
2015-04-08 17:21                 ` Pedro Alves [this message]
2015-04-08 16:27           ` Yao Qi
2015-04-08 16:47             ` 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=552563A2.6050409@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    --cc=sergiodj@redhat.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