public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "t.h.shorrock at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/48750] for_each_template_random_access_ed has unbalanced new/delete[]
Date: Tue, 26 Apr 2011 18:09:00 -0000	[thread overview]
Message-ID: <bug-48750-4-eAa4FpVsZz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48750-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48750

--- Comment #10 from Tom <t.h.shorrock at gmail dot com> 2011-04-26 18:09:05 UTC ---
Hi Paulo,

Yes, this certainly fixes my segfault.

Valgrind complains a little - although I am not sure if this is important (I
am very new to the helgrind tool).  In case it is useful, I attach the
output I get,

So the line numbers are meaningful, I include my modified par_loop.h and my
test file.


Here is my g++ -v

Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
4.4.4-14ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.4 --enable-shared --enable-multiarch
--enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix
--with-gxx-include-dir=/usr/include/c++/4.4 --libdir=/usr/lib --enable-nls
--with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug
--enable-objc-gc --disable-werror --with-arch-32=i686 --with-tune=generic
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)

running on Ubuntu 10-10


Many thanks for your assistance with this. My gratitude to the FSF grows
daily.

Tom



On 26 April 2011 16:20, paolo.carlini at oracle dot com <
gcc-bugzilla@gcc.gnu.org> wrote:

> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48750
>
> --- Comment #9 from Paolo Carlini <paolo.carlini at oracle dot com>
> 2011-04-26 15:19:12 UTC ---
> Seth, Tom, if you get a chance to test the changes I propose in Comment 7
> (suitably, trivially tweaked for 4.4.x), please let me know as soon as
> possible.
>
> If Johannes cannot provide feedback on this issue over the next few days I
> mean
> to go ahead with my patch, likely for 4.6.x too, and work on a other
> similar
> tweaks in the same spirit elsewhere in the parallel code (luckily we have
> only
> an handful of operator new / operator delete pairs needing attention).
>
> --
> Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
>


  parent reply	other threads:[~2011-04-26 18:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-24 11:46 [Bug libstdc++/48750] New: " bugs at sehe dot nl
2011-04-24 11:51 ` [Bug libstdc++/48750] " bugs at sehe dot nl
2011-04-24 12:11 ` paolo.carlini at oracle dot com
2011-04-24 12:16 ` paolo.carlini at oracle dot com
2011-04-24 12:22 ` paolo.carlini at oracle dot com
2011-04-24 12:26 ` paolo.carlini at oracle dot com
2011-04-24 12:54 ` bugs at sehe dot nl
2011-04-24 21:52 ` paolo.carlini at oracle dot com
2011-04-24 22:14 ` paolo.carlini at oracle dot com
2011-04-26 15:21 ` paolo.carlini at oracle dot com
2011-04-26 18:09 ` t.h.shorrock at gmail dot com [this message]
2011-04-26 18:40 ` paolo.carlini at oracle dot com
2011-04-26 18:40 ` paolo.carlini at oracle dot com
2011-04-27  0:57 ` paolo.carlini at oracle dot com
2011-04-27  1:09 ` paolo.carlini at oracle dot com
2011-04-27  9:53 ` bugs at sehe dot nl
2011-04-27 11:17 ` bugs at sehe dot nl
2011-04-27 20:00 ` singler at gcc dot gnu.org
2011-04-27 20:26 ` paolo.carlini at oracle dot com
2011-04-28 16:40 ` rguenth at gcc dot gnu.org
2011-05-03 14:23 ` paolo at gcc dot gnu.org
2011-05-03 15:58 ` bugs at sehe dot nl
2011-05-03 18:03 ` paolo.carlini at oracle dot com
2011-05-03 18:12 ` paolo at gcc dot gnu.org

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=bug-48750-4-eAa4FpVsZz@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).