I honestly don't know. I know my personal use of gdb seems to work most of the time when I'm debugging the class libraries, but it has no idea what the HotSpot frames are. The only other data I have is that others have complained bitterly about how confused gdb gets - though I guess my use is not sophisticated enough to ever notice it.
Sorry, ~Mike On Oct 2, 2009, at 6:47 PM, John Rose wrote: > Thanks for the tip, Mike. I suppose this is the compiler you > mean: /Developer/usr/llvm-gcc-4.2/bin/llvm-gcc-4.2 > > I can't resist asking: Will code from llvm-gcc work better with / > Developer/usr/bin/gdb ? (Obviously I'm hoping for an easy fix.) > > The stack alignment logic on function entry, which gdb appears not > to know about, makes it hopelessly confused about arguments. One > developer I know just switched back to Solaris from Mac because of > this. > > -- John > > On Oct 2, 2009, at 6:29 PM, Mike Swingler wrote: > >> It might also be worth giving llvm-gcc a try, since that is what we >> use to compile the Java SE 6 in Snow Leopard. It uses gcc's front- >> end, and llvm's code generating back-end. I encountered similar >> crashes using GCC 4.2, and they don't look obvious to isolate, let >> alone resolve. >
