_FORTIFY_SOURCE for std::vector

[Paolo Carlini]

On 06/01/2012 03:09 PM, Paolo Carlini wrote:
> You are right, sorry, I went through your changes too quickly and 
> didn't realize that you are just using the existing _M_range_check. 
> Anyway, I confirm that probably we want something more consistent with 
> debug-mode, thus not throwing in this case. Maybe just a 
> __builtin_abort(), I don't know. Or adjust the code in c++config to 
> make available a non-trivial __glibcxx_assert also when 
> _FORTIFY_SOURCE > 0.
Then, if you do this, you probably don't need a new 
_M_fortify_range_check function.

Paolo.