On 08/08/2013 10:48 AM, David Holmes wrote: > On 8/08/2013 7:37 PM, Andrew Haley wrote: >> On 08/08/2013 10:33 AM, David Holmes wrote: >>> With gcc 4.8.1 you are really on the bleeding edge here. Some things >>> will be broken - eg stack walking (used by NativeMemoryTracking and in >>> error reports). >> >> I didn't know. Do you have any more information about that? > > Only just discovered: > > http://bugs.sun.com/view_bug.do?bug_id=8022183 > > A change in gcc 4.6+ but I should clarify it only affects 32-bit apparently.
Thanks. OK, that's no biggie. I am using gcc 4.8 on Aarch64, so things like this tend to worry me. :-) Andrew.
