Open GoogleCodeExporter opened 8 years ago
I'm not going to be able to work on this until September at the earliest. If
someone else would like to take a shot at it, that'd be great.
We should first verify that it is indeed just forward references --- an
implementation limitation of ours --- and not bogus specifications --- a bug of
theirs.
Original comment by jimbla...@gmail.com
on 11 Aug 2011 at 7:09
Not sure if this is useful, but lldb has DWARF reading logic. it seems to be
here:
http://llvm.org/viewvc/llvm-project/lldb/trunk/include/lldb/Symbol/DWARFCallFram
eInfo.h?view=markup
http://llvm.org/viewvc/llvm-project/lldb/trunk/source/Symbol/DWARFCallFrameInfo.
cpp?view=markup
Original comment by thakis@chromium.org
on 11 Aug 2011 at 4:06
I came up with an ugly patch that fixes this. http://breakpad.appspot.com/299001
Jim, assuming I clean it up a little bit, would you have time to review it?
(Before September?)
Original comment by mark@chromium.org
on 11 Aug 2011 at 9:56
Original comment by thakis@chromium.org
on 12 Aug 2011 at 8:57
I think I fixed this on the clang side with 144441.
Original comment by rafael.e...@gmail.com
on 12 Nov 2011 at 4:15
chromium (built with recent clang trunk) still uses the patch
http://breakpad.appspot.com/299001.
I'm wondering if we still need the patch for mac binary (not only chromium)
built with gcc (llvm-gcc) or clang in xcode 4.x.
Original comment by ukai@chromium.org
on 20 Feb 2013 at 7:10
Original issue reported on code.google.com by
mark@chromium.org
on 11 Aug 2011 at 4:23