public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/67747] experimental/filesystem/iterators/recursive_directory_iterator.cc FAILs
Date: Thu, 01 Oct 2015 19:47:00 -0000 [thread overview]
Message-ID: <bug-67747-4-kmiKpXN9gL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67747-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67747
Christophe Lyon <clyon at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |clyon at gcc dot gnu.org
--- Comment #5 from Christophe Lyon <clyon at gcc dot gnu.org> ---
This testcase fails when compiled for armv5t (works for armv7).
I tried the patch proposed in comment #4, but it does not work for me.
However, the error message I can see in gcc.log is:
*** Error in `./directory_iterator.exe': malloc(): memory corruption:
0x40b787f7 ***^M
next prev parent reply other threads:[~2015-10-01 19:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 14:32 [Bug libstdc++/67747] New: " ro at gcc dot gnu.org
2015-09-28 14:32 ` [Bug libstdc++/67747] " ro at gcc dot gnu.org
2015-09-28 14:37 ` redi at gcc dot gnu.org
2015-09-28 14:40 ` redi at gcc dot gnu.org
2015-09-28 14:57 ` ro at CeBiTec dot Uni-Bielefeld.DE
2015-09-28 16:59 ` redi at gcc dot gnu.org
2015-09-29 12:01 ` redi at gcc dot gnu.org
2015-10-01 19:47 ` clyon at gcc dot gnu.org [this message]
2015-10-01 20:30 ` redi at gcc dot gnu.org
2015-10-02 7:36 ` clyon at gcc dot gnu.org
2015-10-02 16:35 ` redi at gcc dot gnu.org
2015-10-02 16:43 ` redi at gcc dot gnu.org
2015-10-07 21:01 ` redi at gcc dot gnu.org
2015-10-07 22:46 ` redi 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-67747-4-kmiKpXN9gL@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).