From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9251] Shared C++ libraries for Microblaze results in Segmentation Fault
Date: Sun, 26 Feb 2017 20:15:10 +0000 [thread overview]
Message-ID: <bug-9251-163-pyOn59Ivd0@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9251-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9251
mail at waldemar-brodkorb.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #5 from mail at waldemar-brodkorb.de ---
I checked with master on x86_64 host.
With gcc 5.x and binutils 2.25.1/2.26.1/2.27.
I couldn't reproduce the segfault anymore.
So may be reopen it with exact version of buildroot, gcc, binutils and
C library used. And if it is happening on x86 or x86_64 host.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2017-02-26 20:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 18:56 [Buildroot] [Bug 9251] New: Shared C++ libraries for Microblaze results in Segmentation Fault bugzilla at busybox.net
2016-09-14 19:07 ` [Buildroot] [Bug 9251] " bugzilla at busybox.net
2016-10-22 19:59 ` bugzilla at busybox.net
2016-10-23 13:39 ` bugzilla at busybox.net
2016-10-24 12:11 ` bugzilla at busybox.net
2017-02-26 20:15 ` bugzilla at busybox.net [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=bug-9251-163-pyOn59Ivd0@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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