public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Pedro Alves'" <palves@redhat.com>,
	"'Sergio Durigan Junior'" <sergiodj@redhat.com>
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 16:28:00 -0000	[thread overview]
Message-ID: <001c01d07218$fd5daa20$f818fe60$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <552545B3.9000402@redhat.com>



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Pedro Alves
> Envoyé : mercredi 8 avril 2015 17:14
> À : Pierre Muller; 'Sergio Durigan Junior'
> Cc : 'GDB Patches'
> Objet : Re: Build failure following: Implement support for checking
> /proc/PID/coredump_filter commit
> 
> On 04/08/2015 03:43 PM, Pedro Alves wrote:
> > On 04/08/2015 03:07 PM, Pierre Muller wrote:
> >
> >> Or maybe we should use the gnulib version of strtok_r?
> >
> > Yes.
> >
> >> I don't really know how to do this, but if someone can tell me,
> >> I can test the patch.
> >
> > Let me give that a try, and I'll post a branch for you to test.
> 
> Please try the users/palves/gnulib-strtok_r branch.

I can confirm that I am able to build mingw32 64bit gdb.exe executable,
and it contains gnulib/import/strtok_r.c source.

  I am not really able to test that the code works OK,
as I don't really know how to trigger that code...

  I have no idea what we should do now...

Pierre Muller

  parent reply	other threads:[~2015-04-08 16:28 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 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 [this message]
2015-04-08 16:47               ` Sergio Durigan Junior
2015-04-08 17:21                 ` Pedro Alves
2015-04-08 16:27           ` Yao Qi
2015-04-08 16:47             ` Pedro Alves
2015-03-24 23:57 ` [PATCH 2/2] Documentation and testcase Sergio Durigan Junior
2015-03-27  9:53   ` 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='001c01d07218$fd5daa20$f818fe60$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).