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 temp
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 m
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 #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 use
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
Randy changed:
What|Removed |Added
CC||Randy at miningrigrentals dot
com
--- Comment #
