On 2012-12-18 22:12, George Liaskos wrote:
Try removing --gc-sections from the link flags for protoc, that should
solve it for now. I am still looking at the root cause, which seems to
be something in our ld; it does not seem to be related to either clang
or libstdc++.
Whoa, thank you! Removin
> Try removing --gc-sections from the link flags for protoc, that should
> solve it for now. I am still looking at the root cause, which seems to
> be something in our ld; it does not seem to be related to either clang
> or libstdc++.
Whoa, thank you! Removing --gc-sections from the link flags so
On 2012-12-18 13:21, René Ladan wrote:
the following backtrace is from a crash that happened when building
www/chromium with clang. The chromium port builds a binary protoc which
crashes when built with clang.
...
So the question is if this is a protoc or a clang or a libstdc++ bug.
Try remo
==90885== Memcheck, a memory error detector
==90885== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==90885== Using Valgrind-3.8.0 and LibVEX; rerun with -h for copyright info
==90885== Command: ./protoc
==90885==
==90885== Invalid read of size 8
==90885==at 0x1388506: std::os
On Tue, Dec 18, 2012 at 01:21:42PM +0100, Ren? Ladan wrote:
> Hi,
>
> the following backtrace is from a crash that happened when building
> www/chromium with clang. The chromium port builds a binary protoc which
> crashes when built with clang.
>
> Program received signal SIGSEGV, Segmentation f
Hi,
the following backtrace is from a crash that happened when building
www/chromium with clang. The chromium port builds a binary protoc which
crashes when built with clang.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 802006400 (LWP 100869)]
0x000800996506 in s
