[Bug libstdc++/48257] New: std::string::assign() corrupts std::string static data when called on emptyString1 using emptyString2.data()

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48257 Summary: std::string::assign() corrupts std::string static data when called on emptyString1 using emptyString2.data() Product: gcc Version: 4.1.2 Status: UNCONFIRMED

[Bug libstdc++/48257] std::string::assign() corrupts std::string static data when called on emptyString1 using emptyString2.data()

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48257 Mohsin changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID

[Bug libstdc++/48257] std::string::assign() corrupts std::string static data when called on emptyString1 using emptyString2.data()

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48257 Mohsin changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID

[Bug libstdc++/48257] std::string::assign() corrupts std::string static data when called on emptyString1 using emptyString2.data()

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48257 --- Comment #8 from Mohsin 2011-03-24 09:50:11 UTC --- (In reply to comment #6) > Also, GCC 4.1.2 is ancient and not supported here, you should either report > bugs to the vendor of your version (Red Hat) or refer to a supported version.

[Bug libstdc++/48257] std::string::assign() corrupts std::string static data when called on emptyString1 using emptyString2.data()

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48257 --- Comment #9 from Mohsin 2011-03-24 09:52:56 UTC --- (In reply to comment #7) > (In reply to comment #4) > > > > I don't see any errors being thrown. I am not trying to nit-pick but I've > > raised this issue because I was affected by

[Bug libstdc++/48257] std::string::assign() corrupts std::string static data when called on emptyString1 using emptyString2.data()

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48257 --- Comment #10 from Mohsin 2011-03-24 10:21:56 UTC --- Two questions here: 1. Is the behaviour undefined for __n < number of elements in __s? 2. For cases undefined in the specs, do we take steps to ensure robustness? I still cannot

[Bug libstdc++/48257] std::string::assign() corrupts std::string static data when called on emptyString1 using emptyString2.data()

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48257 --- Comment #11 from Mohsin 2011-03-24 10:24:15 UTC --- (In reply to comment #10) > Two questions here: > > 1. Is the behaviour undefined for __n < number of elements in __s? > Oops! I meant for __n > number of elements in __s.

[Bug libstdc++/48257] std::string::assign() corrupts std::string static data when called on emptyString1 using emptyString2.data()

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48257 --- Comment #13 from Mohsin 2011-03-25 05:48:21 UTC --- (In reply to comment #12) > (In reply to comment #11) > > (In reply to comment #10) > > > Two questions here: > > > > > > 1. Is the behaviour undefined for __n < number of elements in __s?