On 08/05/18 16:51 -0700, Ian Lance Taylor via libstdc++ wrote:
On Tue, May 8, 2018 at 12:54 PM, François Dumont wrote:
I'll go with this version for now but I'll look into libbacktrace.
It will be perhaps the occasion to play with autoconf & al tools to find out
if I can use libbacktrace.
I
On Tue, May 8, 2018 at 12:54 PM, François Dumont wrote:
>
> I'll go with this version for now but I'll look into libbacktrace.
>
> It will be perhaps the occasion to play with autoconf & al tools to find out
> if I can use libbacktrace.
In GCC libgo and libgfortran already use libbacktrace, so th
On 08/05/2018 17:27, Jonathan Wakely wrote:
On 07/05/18 22:20 +0200, François Dumont wrote:
Hi
Here is the patch to add backtrace info to debug assertion
failure output.
Example:
/home/fdt/dev/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/debug/vector:188:
In function:
std::
On 07/05/18 22:20 +0200, François Dumont wrote:
Hi
Here is the patch to add backtrace info to debug assertion failure
output.
Example:
/home/fdt/dev/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/debug/vector:188:
In function:
std::__debug::vector<_Tp, _Allocator>::vector(_InputI
Hi
Here is the patch to add backtrace info to debug assertion failure
output.
Example:
/home/fdt/dev/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/debug/vector:188:
In function:
std::__debug::vector<_Tp, _Allocator>::vector(_InputIterator,
_InputIterator, const _Allocator&) [
