From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9251] New: Shared C++ libraries for Microblaze results in Segmentation Fault
Date: Wed, 14 Sep 2016 18:56:31 +0000 [thread overview]
Message-ID: <bug-9251-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9251
Bug ID: 9251
Summary: Shared C++ libraries for Microblaze results in
Segmentation Fault
Product: buildroot
Version: 2016.08
Hardware: Other
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: scotttimothye at johndeere.com
CC: buildroot at uclibc.org
Target Milestone: ---
It appears that enabling C++ and shared libraries does not work for Microblaze
targets. When a simple Hello World C++ application is executed, it results in
a Segmentation Fault. This occurs before any code in the app is executed
(presumably the fault is occurring in the libstdc++ startup code.)
Host environment: Linux Mint 15, 32-bit x86 platform. wbx has also replicated
it on an x86_64 system with similar results.
Steps to reproduce using buildroot git hash
ed5604ed9e378c3f8814d7f92ec66fd855b8245c:
1) make qemu_microblazeel_mmu_defconfig
2) make menuconfig
- Toolchain: enable C++ support
3) make
4) cat > hello.cpp
int main(void){}
5) output/host/usr/bin/microblazeel-linux-g++ hello.cpp -o
output/target/root/hello
6) make
7) Running qemu 2.5.1.1:
qemu-system-microblazeel -M petalogix-s3adsp1800 -serial stdio -kernel
output/images/linux.bin
8) Let the system boot. Login w/password "root"
9) ./hello
-> Segmentation Fault.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-09-14 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 18:56 bugzilla at busybox.net [this message]
2016-09-14 19:07 ` [Buildroot] [Bug 9251] Shared C++ libraries for Microblaze results in Segmentation Fault 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
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@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