public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Ian Lance Taylor via gcc-patches" <gcc-patches@gcc.gnu.org>
To: Tom de Vries <tdevries@suse.de>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, Ian Lance Taylor <ian@airs.com>
Subject: Re: [PATCH][libbacktrace] Add allocfail.sh test-case
Date: Wed, 12 Dec 2018 13:40:00 -0000	[thread overview]
Message-ID: <CAKOQZ8yX1FHzp9RTMRyU4=R6A7bp4Z74JO9M-F4KCDNaO_aQEA@mail.gmail.com> (raw)
In-Reply-To: <51acefeb-6862-66c9-d291-bcc9b4696afd@suse.de>

On Tue, Dec 11, 2018 at 11:04 PM Tom de Vries <tdevries@suse.de> wrote:
>
> [ Fixed ENOPATCH ]
>
> On 12-12-18 08:03, Tom de Vries wrote:
> > On 11-12-18 18:59, Ian Lance Taylor wrote:
> >> On Wed, Nov 28, 2018 at 4:50 AM Tom de Vries <tdevries@suse.de> wrote:
> >>>
> >>> Add test-case that forces alloc.c functions to fail, and check whether fail
> >>> handling is robust.
> >>>
> >>> This is the test-case for "[libbacktrace] Fix segfault upon allocation
> >>> failure".  Without that patch, this test-case fails like this:
> >>> ...
> >>> allocfail.sh: line 71: 26041 Segmentation fault      (core dumped) \
> >>>   ./allocfail $i > /dev/null 2>&1
> >>> Unallowed fail found: 13
> >>> FAIL allocfail.sh (exit status: 1)
> >>> ...
> >>>
> >>> This is a seperate patch because the test-case is nontrivial.
> >>>
> >>> Bootstrapped and reg-tested on x86_64.
> >>>
> >>> OK for trunk?
> >>>
> >>> Thanks,
> >>> - Tom
> >>>
> >>> [libbacktrace] Add allocfail.sh test-case
> >>>
> >>> 2018-11-27  Tom de Vries  <tdevries@suse.de>
> >>>
> >>>         * Makefile.am (TESTS): Add allocfail.sh.
> >>>         (check_PROGRAMS): Add allocfail.
> >>>         * Makefile.in: Regenerate.
> >>>         * instrumented_alloc.c: New file.  Redefine malloc and realloc.
> >>>         Include alloc.c.
> >>>         * allocfail.c: New file.
> >>>         * allocfail.sh: New file.
> >>
> >> Can you redo this without using GNU make features like $(filter-out) ?
> >
> > Hi,
> >
> > Done, and re-bootstrapped-and-regtested.
> >
> > OK for trunk?

This is OK.

Thanks.

Ian

      reply	other threads:[~2018-12-12 13:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28 12:49 Tom de Vries
2018-12-11 17:59 ` Ian Lance Taylor via gcc-patches
2018-12-12  7:02   ` Tom de Vries
2018-12-12  7:04     ` Tom de Vries
2018-12-12 13:40       ` Ian Lance Taylor via gcc-patches [this message]

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='CAKOQZ8yX1FHzp9RTMRyU4=R6A7bp4Z74JO9M-F4KCDNaO_aQEA@mail.gmail.com' \
    --to=gcc-patches@gcc.gnu.org \
    --cc=ian@airs.com \
    --cc=iant@google.com \
    --cc=tdevries@suse.de \
    /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).