470,594 Members | 1,534 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,594 developers. It's quick & easy.

map<string,set<strin> > compilation problem

Hi all,

In a class of mine I tried to use the following member:

std::map<std::string, std::set<std::string> > m_files;

but I recieved the following error message:

mips-tfile, /tmp/cceNEN7W.s:286 String too big (5071 bytes)
line: #.stabs "lower_bound::1317:_ZNSt8_Rb_treeISsSt4
pairIKSsSt3setISsSt4lessISsESaISsEEESt10_Select1st IS7_ES4_SaIS7
_EE11lower_boundERS1_;2A.1318:_ZNKSt8_Rb_treeISsSt 4pairIKSsSt3s
etISsSt4lessISsESaISsEEESt10_Select1stIS7_ES4_SaIS 7_EE11lower_b
oundERS1_;2B.;upper_bound::1317:_ZNSt8_Rb_treeISsS t4pairIKSsSt3
setISsSt4lessISsESaISsEEESt10_Select1stIS7_ES4_SaI S7_EE11upper_
boundERS1_;2A.1318

and the message continues in this criptographic pattern for more 30 or 40 lines.

I am using gcc 3.0.2 on a Tru64 machine.

Did I do something wrong? Is this expected? Is there a workaround?

Thanks.

Marcelo Pinto
Jul 22 '05 #1
4 2231
"Marcelo Pinto" <mp****@brturbo.com> wrote...
In a class of mine I tried to use the following member:

std::map<std::string, std::set<std::string> > m_files;

but I recieved the following error message:

mips-tfile, /tmp/cceNEN7W.s:286 String too big (5071 bytes)
line: #.stabs "lower_bound::1317:_ZNSt8_Rb_treeISsSt4
pairIKSsSt3setISsSt4lessISsESaISsEEESt10_Select1st IS7_ES4_SaIS7
_EE11lower_boundERS1_;2A.1318:_ZNKSt8_Rb_treeISsSt 4pairIKSsSt3s
etISsSt4lessISsESaISsEEESt10_Select1stIS7_ES4_SaIS 7_EE11lower_b
oundERS1_;2B.;upper_bound::1317:_ZNSt8_Rb_treeISsS t4pairIKSsSt3
setISsSt4lessISsESaISsEEESt10_Select1stIS7_ES4_SaI S7_EE11upper_
boundERS1_;2A.1318

and the message continues in this criptographic pattern for more 30 or 40 lines.
I am using gcc 3.0.2 on a Tru64 machine.

Did I do something wrong? Is this expected? Is there a workaround?


Try the usual typedef workaround:

typedef std::string str;
typedef std::set<str> strset;
typedef std::map<str, strset> strsetmap;

and then

strsetmap m_files;

HTH

Victor
Jul 22 '05 #2
"Victor Bazarov" <v.********@comAcast.net> wrote in message news:<6BiLc.128796$a24.30465@attbi_s03>...

Try the usual typedef workaround:

typedef std::string str;
typedef std::set<str> strset;
typedef std::map<str, strset> strsetmap;

and then

strsetmap m_files;

HTH

Victor


I tryed your sugestion and it didn't work.
[OT]
Then I realized that if I didn't use the -g option the source get
compiled just fine.

Are you aware of the reason why this is so?

[/OT]

Thanks,

Marcelo Pinto
Jul 22 '05 #3
Marcelo Pinto wrote:
"Victor Bazarov" <v.********@comAcast.net> wrote in message news:<6BiLc.128796$a24.30465@attbi_s03>...
Try the usual typedef workaround:

typedef std::string str;
typedef std::set<str> strset;
typedef std::map<str, strset> strsetmap;

and then

strsetmap m_files;

HTH

Victor

I tryed your sugestion and it didn't work.
[OT]
Then I realized that if I didn't use the -g option the source get
compiled just fine.

Are you aware of the reason why this is so?


No, nor is it topical to comp.lang.c++. Try a newsgroup for your
compiler. Compiler options, name mangling, format of object files,
and so on, are not language-defined.

If there is no newsgroup that deals with your compiler, try the one
that deals with your OS. If none exists, try the technical support
for your compiler or/and OS.

V
Jul 22 '05 #4
Marcelo Pinto wrote:
mips-tfile, /tmp/cceNEN7W.s:286 String too big (5071 bytes)
line: #.stabs "lower_bound::1317:_ZNSt8_Rb_treeISsSt4
pairIKSsSt3setISsSt4lessISsESaISsEEESt10_Select1st IS7_ES4_SaIS7
_EE11lower_boundERS1_;2A.1318:_ZNKSt8_Rb_treeISsSt 4pairIKSsSt3s
etISsSt4lessISsESaISsEEESt10_Select1stIS7_ES4_SaIS 7_EE11lower_b
oundERS1_;2B.;upper_bound::1317:_ZNSt8_Rb_treeISsS t4pairIKSsSt3
setISsSt4lessISsESaISsEEESt10_Select1stIS7_ES4_SaI S7_EE11upper_
boundERS1_;2A.1318

I am using gcc 3.0.2 on a Tru64 machine.


This gcc bug was corrected in may 2003, you should upgrade your
compiler.
Jul 22 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by champagne | last post: by
2 posts views Thread by Connell Gauld | last post: by
reply views Thread by Adriano Coser | last post: by
4 posts views Thread by Marcelo | last post: by
1 post views Thread by Agathamk | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.