#72 libstdc++ case fails for bad_alloc on bf533-stamp

Milestone: 2012R2

Status: open

Owner: nobody

Labels: None

Priority: middle

Resolution: none

Processor: BF533

Processor revision:

Updated: 2014-02-17

Created: 2013-07-05

Creator: panmingquan

Private: No

[#7382] libstdc++ case fails for bad_alloc on bf533-stamp
Move Item | Delete Item | Clone Item | Merge Item
Submitted By: Mingquan Pan
Open Date
2012-10-09 16:54:38
Priority:
Assignee:
State:
Found In Release:
Is this bug repeatable?:
Board:
Silicon Revision:
Resolution:
Fixed In Release:
Processor:
Host Operating System:
kernel rev.:
toolchain rev.:
Summary:
Details: (Edit)

libstdc++ case fails for bad_alloc on bf533-stamp. It isn't seen on bf537-stamp board.

Comparing libstdc++-4.3.sum

Tests that now fail, but worked before:

bfin-linux-uclibc: 27_io/basic_istream/extractors_character/wchar_t/4.cc execution test
bfin-linux-uclibc: 27_io/basic_istream/getline/wchar_t/5.cc execution test
bfin-linux-uclibc: 27_io/basic_istream/ignore/wchar_t/2.cc execution test
bfin-linux-uclibc: tr1/6_containers/unordered_set/26132.cc execution test

Executing on host: bfin-linux-uclibc-g++ -g -O2 -D_GLIBCXX_ASSERT -fmessage-length=0 -DLOCALEDIR="." -I/home/test/work/cruise/checkouts/toolchain/gcc-4.3/libstdc++-v3/testsuite/util /home/test/work/cruise/checkouts/toolchain/gcc-4.3/libstdc++-v3/testsuite/tr1/6_containers/unordered_set/26132.cc ./libtestc++.a -lm -mcpu=bf533-0.3 -o ./26132.exe (timeout = 600)
spawn bfin-linux-uclibc-g++ -g -O2 -D_GLIBCXX_ASSERT -fmessage-length=0 -DLOCALEDIR="." -I/home/test/work/cruise/checkouts/toolchain/gcc-4.3/libstdc++-v3/testsuite/util /home/test/work/cruise/checkouts/toolchain/gcc-4.3/libstdc++-v3/testsuite/tr1/6_containers/unordered_set/26132.cc ./libtestc++.a -lm -mcpu=bf533-0.3 -o ./26132.exe^M
PASS: tr1/6_containers/unordered_set/26132.cc (test for excess errors)
Executing on bfin-linux-uclibc: /tmp/26132.exe.18085 {} {} (timeout = 300)
spawn [open ...]^M
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
ABRT
XYZ134ZYX
Executing on bfin-linux-uclibc: rm -f /tmp/26132.exe.18085 (timeout = 300)
spawn [open ...]^M
XYZ0ZYX
Executed ./26132.exe, status 1
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
ABRT
FAIL: tr1/6_containers/unordered_set/26132.cc execution test
extra_tool_flags are:

Follow-ups

--- Mingquan Pan 2012-10-11 17:14:30
On bf537-stamp, only one case fails like:

--- Mingquan Pan 2012-11-19 13:55:34
Sometimes this issue also happens to libstdc++ case on bf537-stamp.

Comparing libstdc++-4.3.sum

Tests that now fail, but worked before:

bfin-uclinux: 27_io/basic_istream/extractors_character/wchar_t/4.cc execution
test
bfin-uclinux: 27_io/basic_istream/getline/wchar_t/5.cc execution test

Executing on host: bfin-uclinux-g++ -g -O2 -D_GLIBCXX_ASSERT -fmessage-length=0
-DLOCALEDIR="."
-I/home/test/work/cruise/checkouts/toolchain/gcc-4.3/libstdc++-v3/testsuite/util
/home/test/work/cruise/checkouts/toolchain/gcc-4.3/libstdc++-v3/testsuite/27_io/basic_istream/extractors_character/wchar_t/4.cc
./libtestc++.a -Wl,-elf2flt=-s120000 -lm -mcpu=bf537-0.2 -o ./4.exe
(timeout = 600)
spawn bfin-uclinux-g++ -g -O2 -D_GLIBCXX_ASSERT -fmessage-length=0
-DLOCALEDIR="."
-I/home/test/work/cruise/checkouts/toolchain/gcc-4.3/libstdc++-v3/testsuite/util
/home/test/work/cruise/checkouts/toolchain/gcc-4.3/libstdc++-v3/testsuite/27_io/basic_istream/extractors_character/wchar_t/4.cc
./libtestc++.a -Wl,-elf2flt=-s120000 -lm -mcpu=bf537-0.2 -o ./4.exe^M
PASS: 27_io/basic_istream/extractors_character/wchar_t/4.cc (test for excess
errors)
Executing on bfin-uclinux: /tmp/4.exe.4469 {} {} (timeout = 300)
spawn [open ...]^M
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
ABRT
XYZ134ZYX
Executing on bfin-uclinux: rm -f /tmp/4.exe.4469 (timeout = 300)
spawn [open ...]^M
XYZ0ZYX
Executed ./4.exe, status 1
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
ABRT
FAIL: 27_io/basic_istream/extractors_character/wchar_t/4.cc execution test
extra_tool_flags are:
...
Executing on host: bfin-uclinux-g++ -g -O2 -D_GLIBCXX_ASSERT -fmessage-length=0
-DLOCALEDIR="."
-I/home/test/work/cruise/checkouts/toolchain/gcc-4.3/libstdc++-v3/testsuite/util
/home/test/work/cruise/checkouts/toolchain/gcc-4.3/libstdc++-v3/testsuite/27_io/basic_istream/getline/wchar_t/5.cc
./libtestc++.a -Wl,-elf2flt=-s120000 -lm -mcpu=bf537-0.2 -o ./5.exe
(timeout = 600)
spawn bfin-uclinux-g++ -g -O2 -D_GLIBCXX_ASSERT -fmessage-length=0
-DLOCALEDIR="."
-I/home/test/work/cruise/checkouts/toolchain/gcc-4.3/libstdc++-v3/testsuite/util
/home/test/work/cruise/checkouts/toolchain/gcc-4.3/libstdc++-v3/testsuite/27_io/basic_istream/getline/wchar_t/5.cc
./libtestc++.a -Wl,-elf2flt=-s120000 -lm -mcpu=bf537-0.2 -o ./5.exe^M
PASS: 27_io/basic_istream/getline/wchar_t/5.cc (test for excess errors)
Executing on bfin-uclinux: /tmp/5.exe.4469 {} {} (timeout = 300)
spawn [open ...]^M
sh: can't execute '/tmp/5.exe.4469': Cannot allocate memory
XYZ127ZYX
Executing on bfin-uclinux: rm -f /tmp/5.exe.4469 (timeout = 300)
spawn [open ...]^M
XYZ0ZYX
Executed ./5.exe, status 1
sh: can't execute '/tmp/5.exe.4469': Cannot allocate memory
FAIL: 27_io/basic_istream/getline/wchar_t/5.cc execution test
extra_tool_flags are:

It doesn't always happening, but do affect the testing from time to time.

--- Mingquan Pan 2012-12-13 16:54:58
After increasing stacksize to 200000, it looks the uclinux test log improves and
not seeing "Cannot allocate memory" error now.
But 'std::bad_alloc' still exists(this is not regression bug). like:

Executing on host: bfin-uclinux-g++ -g -O2 -D_GLIBCXX_ASSERT
-fmessage-length=0 -DLOCALEDIR="."
-I/home/test/workspace/src/toolchain/gcc-4.3/libstdc++-v3/testsuite/util
/home/test/workspace/src/toolchain/gcc-4.3/libstdc++-v3/testsuite/27_io/basic_stringbuf/overflow/wchar_t/1.cc
./libtestc++.a -Wl,-elf2flt=-s200000 -lm -mcpu=bf537-0.2 -o ./1.exe
(timeout = 600)
spawn bfin-uclinux-g++ -g -O2 -D_GLIBCXX_ASSERT -fmessage-length=0
-DLOCALEDIR="."
-I/home/test/workspace/src/toolchain/gcc-4.3/libstdc++-v3/testsuite/util
/home/test/workspace/src/toolchain/gcc-4.3/libstdc++-v3/testsuite/27_io/basic_stringbuf/overflow/wchar_t/1.cc
./libtestc++.a -Wl,-elf2flt=-s200000 -lm -mcpu=bf537-0.2 -o ./1.exe^M
PASS: 27_io/basic_stringbuf/overflow/wchar_t/1.cc (test for excess errors)
Executing on bfin-uclinux: /tmp/1.exe.11819 {} {} (timeout = 300)
spawn [open ...]^M
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
ABRT
XYZ134ZYX
Executing on bfin-uclinux: rm -f /tmp/1.exe.11819 (timeout = 300)
spawn [open ...]^M
XYZ0ZYX
Executed ./1.exe, status 1
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
ABRT
FAIL: 27_io/basic_stringbuf/overflow/wchar_t/1.cc execution test
extra_tool_flags are:

--- Stuart Henderson 2012-12-17 23:18:25
Yeah, those have always failed. in the handful of tests i've looked at, it
would be pretty easy to adjust the test to be slightly less memory intensive.
are the failures causing a problem for you?

--- Mingquan Pan 2012-12-20 14:36:48
Yes, I would like these cases are changed to be less memory intensive so that
they can pass in the test log.

Discussion

Sonic Zhang - 2013-07-09

Priority: 3 --> middle
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

libstdc++ case fails for bad_alloc on bf533-stamp

The GNU Toolchain for ADI's Blackfin and future processors

Found in Release

Searches

Help

#72 libstdc++ case fails for bad_alloc on bf533-stamp

Comparing libstdc++-4.3.sum

Comparing libstdc++-4.3.sum

Discussion