Discussions
Categories
- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
Studio 12.6 / Solaris 11.3 amd64 "Assertion: (../lnk/inline.cc, line 1120)"

Hi,
known problem?
$ CC -V
CC: Studio 12.6 Sun C++ 5.15 SunOS_i386 2017/05/30
$ cat vec.cc
#include <iostream>
#include <string>
#include <vector>
using namespace std;
int
main(void)
{
vector<string> vs;
string s = "one";
vs.push_back(s);
cout << vs.at(0) << endl;
return 0;
}
$ CC -xcheck=%all -library=stlport4 vec.cc
>> Assertion: (../lnk/inline.cc, line 1120)
while processing vec.cc at line 0.
Best Answer
-
Thanks for reporting this problem. I was able to reproduce it. The bug seems to be triggered by the combination of using iostream output and the -xcheck=init_local sub-option. (Other operations might also trigger it, of course.)
I have filed bug 26396699 for the problem.
Possible workaround: Use
-xcheck=%all,no%init_local
to turn off just the check that results in the assertion.
Answers
-
Thanks for reporting this problem. I was able to reproduce it. The bug seems to be triggered by the combination of using iostream output and the -xcheck=init_local sub-option. (Other operations might also trigger it, of course.)
I have filed bug 26396699 for the problem.
Possible workaround: Use
-xcheck=%all,no%init_local
to turn off just the check that results in the assertion.