https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
--- Comment #43 from Jonathan Wakely ---
And updating vstring is exactly what I'd like to avoid. It's pretty much on
life support as far as I'm concerned.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
--- Comment #42 from Randy ---
(In reply to Jonathan Wakely from comment #41)
> So then basically the same as what I said:
>
> (In reply to Jonathan Wakely from comment #37)
> > (Your segfaults are probably because you're using c_str() on a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
--- Comment #41 from Jonathan Wakely ---
So then basically the same as what I said:
(In reply to Jonathan Wakely from comment #37)
> (Your segfaults are probably because you're using c_str() on a temporary
> string, so accessing the pointer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
--- Comment #40 from Randy ---
(In reply to Jonathan Wakely from comment #39)
> (In reply to Randy from comment #38)
> > std::string is not thread safe, this is why vstring is used (from my
> > memory).
>
> That's totally wrong, vstring has no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
--- Comment #39 from Jonathan Wakely ---
(In reply to Randy from comment #38)
> std::string is not thread safe, this is why vstring is used (from my
> memory).
That's totally wrong, vstring has no more thread-safety than std::string has.
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
--- Comment #38 from Randy ---
(In reply to Jonathan Wakely from comment #37)
> Please report a separate bug for vstring then.
>
> (Your segfaults are probably because you're using c_str() on a temporary
> string, so accessing the pointer after
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
--- Comment #37 from Jonathan Wakely ---
Please report a separate bug for vstring then.
(Your segfaults are probably because you're using c_str() on a temporary
string, so accessing the pointer after the temporary goes out of scope.)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
--- Comment #36 from Randy ---
(In reply to Jonathan Wakely from comment #35)
> As you can see from the commit above, nothing was changed in
> __gnu_cxx::vstring (there is no "std_vstring").
Ok then can someone look at __gnu_cxx::vstring, we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
--- Comment #35 from Jonathan Wakely ---
As you can see from the commit above, nothing was changed in __gnu_cxx::vstring
(there is no "std_vstring").
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
Randy changed:
What|Removed |Added
CC||Randy at miningrigrentals dot
com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
Martin Sebor changed:
What|Removed |Added
Known to fail|11.0|
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
Martin Sebor changed:
What|Removed |Added
Target Milestone|11.0|12.0
--- Comment #32 from Martin Sebor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
Jakub Jelinek changed:
What|Removed |Added
Summary|[11 Regression] Bogus |Bogus -Wstringop-overread
13 matches
Mail list logo
