From: Joel Brobecker <brobecker@adacore.com>
To: Bernhard Heckel <bernhard.heckel@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] testsuite: Fix run to main issue introduced by GCC 5.x.
Date: Fri, 26 Feb 2016 16:55:00 -0000 [thread overview]
Message-ID: <20160226165520.GH5599@adacore.com> (raw)
In-Reply-To: <1456152558-3962-3-git-send-email-bernhard.heckel@intel.com>
Hello,
On Mon, Feb 22, 2016 at 03:49:17PM +0100, Bernhard Heckel wrote:
> From: "bernhard.heckel" <bernhard.heckel@intel.com>
>
> Adding an dummy assignment as an new breakpoint anchor because
"an dummy" -> "a dummy"; same for "an new" -> "a new".
> breakpoint on return statement doesn't work for GCC 5.x.
"the breakpoint on the return statement".
> 2016-02-16 Bernhard Heckel <bernhard.heckel@intel.com>
>
> gdb/Changelog:
>
> * vla-cxx.cc: Insert dummy assignment as anchor for an breakpoint.
Same remark as before for the name of the ChangeLog file and the name
of the file being changed.
Ok with those changes.
--
Joel
next prev parent reply other threads:[~2016-02-26 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 14:49 [PATCH] Fix detection of gfortran compilers Bernhard Heckel
2016-02-22 14:50 ` [PATCH] testsuite: Fix timeout issues during print of vla-arrays Bernhard Heckel
2016-02-23 19:37 ` Luis Machado
2016-02-24 8:03 ` Heckel, Bernhard
2016-02-24 14:47 ` Yao Qi
2016-02-25 13:16 ` Heckel, Bernhard
2016-02-22 14:50 ` [PATCH] testsuite: Fix run to main issue introduced by GCC 5.x Bernhard Heckel
2016-02-26 16:55 ` Joel Brobecker [this message]
2016-03-02 15:44 ` Heckel, Bernhard
2016-02-22 14:50 ` [PATCH] testsuite: Nullify pointers before first usage Bernhard Heckel
2016-02-26 16:49 ` Joel Brobecker
2016-03-02 15:45 ` Heckel, Bernhard
2016-02-26 16:47 ` [PATCH] Fix detection of gfortran compilers Joel Brobecker
2016-03-02 15:45 ` Heckel, Bernhard
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=20160226165520.GH5599@adacore.com \
--to=brobecker@adacore.com \
--cc=bernhard.heckel@intel.com \
--cc=gdb-patches@sourceware.org \
/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