When I’ve seen this happen before and was able to isolate a cause, it involved namespaces or templates or both.  
I don’t recall the specifics.  I’m trying to reproduce the problem locally at r43824.  If I can, then I’ll take a look at 
what’s changing in V8 at that revision.  That may jog my memory.

Mark, it would be great if you could have a look since I don't have a mac to reproduce 
this. The V8 revision range for that roll is r4302 to r4347. The revision range is 
small, so changing the DEPS file to pull from V8 branches/bleeding_edge@revision a 
binary search in revisions should isolate the change causing this quickly.

Also, be aware that we have reverted that change yesterday so we are currently back at 
a previous V8 revision (because of a new reliability crash).  We will probably roll it 
forward again today, but when attempting to reproduce you might want to change DEPS to 
pull from branches/bleeding_edge r4347.

Since I wasn't able to reproduce this ld crash, maybe someone who was (Robert or Rohit) can work out which V8 
revision triggers this.

fyi - i wasn't able to repro it on my machines either.

I'll work on finding it, most likely tonight or tomorrow.

(No comment was entered for this change.)

I'm not seeing this anymore and Rohit said in IRC he wasn't either. Closing for now.

Thanks to mmentovai for getting ld64-97.2 to build, we got a core dump from ld narrowing down the problem 
to a name mangling bug in gcc where part of the namespace name (the "2" in "gles2") is being conflated with the 
length of a portion of the mangled name. See the following thread:

http://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/thread/71e4b5bd088cd6f1#

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=47225 

------------------------------------------------------------------------
r47225 | kbr@google.com | 2010-05-13 17:06:54 -0700 (Thu, 13 May 2010) | 8 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/gpu/command_buffer/client/gles2_lib.cc?r1=47225&r2=47224

Work around bug in gcc's name mangling causing linker to crash on Mac
OS X.

BUG=40845
TEST=none
TBR=gman

Review URL: http://codereview.chromium.org/2079003
------------------------------------------------------------------------

Rohit and I have been unable to build Chromium because ld segfaults while linking Chromium 
Framework. We bisected down and found that the V8 roll at r43824 was the culprit:

http://src.chromium.org/viewvc/chrome?view=rev&revision=43824

System Info:

[chrome] rsesek% sw_vers 
ProductName:	Mac OS X
ProductVersion:	10.6.3
BuildVersion:	10D573

[chrome] rsesek% uname -a
Darwin copernicus 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST 2010; root:xnu-
1504.3.12~1/RELEASE_I386 i386

[chrome] rsesek% xcodebuild -version
Xcode 3.2.2
Component versions: DevToolsCore-1648.0; DevToolsSupport-1631.0
BuildVersion: 10M2148

[chrome] rsesek% ld -v              
@(#)PROGRAM:ld  PROJECT:ld64-97.2
llvm version 2.6svn,  Apple Build #2207-05

This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.

(No comment was entered for this change.)