| Hi Quincey,
Thanks for taking time to look at it.
If it's an alignment/offset issue, why the two '1's repeated at the end of the array ? I sure hope it's something fixable, but Ive had many problems the last couple of days relating to the debugger, both using gcc and llvm as compiler, and using gdb and lldb for debugging respectively. the problem reported here pertains to llvm gcc 4.2 as compiler and lldb as debugger. when I compile with gcc and use gdb as the debugger, things do seem to work properly, however I get the following message in the console for which I don't understand the cause and im unsure whether it's related:
warning: Unable to read symbols for /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.3.2 (8H7)/Symbols/Developer/usr/lib/libXcodeDebuggerSupport.dylib (file not found). warning: No copy of libXcodeDebuggerSupport.dylib found locally, reading from memory on remote device. This may slow down the debug session.
I'm not quite sure why you're talking about 'ivar's, could you explain ? the m_v array is an array of floats - not integers, or do I misunderstand your use of the word ivar ?.
J
On Aug 16, 2011, at 11:49 PM, Quincey Morris wrote: On Aug 16, 2011, at 14:27 , J wrote: I'm having such serious problems with the debuggers in Xcode 4.1 on Lion that it's impairing production. With deadline looming, it is very frustrating to have our primary tool crash every other launch. The latest issue however really baffles me. Is there anyone who can explain the discrepancy between the left and right panes in the image linked to below ? the right pane - the printed output is the expected output. However, the variables view shows a completely different layout of the values in the matrix, which has a float m_v[16] member which is printed. the image is on
It's not a "completely different layout". It looks like the ivar display is actually starting at index 2 and perhaps displaying the 1st 2 floats of the next ivar for the last 2 indexes.
If you're getting this result in both lldb and gdb, I'd suspect that the debug information being generated for the class is wrong. Perhaps this is a structure alignment issue for the ivar layout, perhaps just a random bug. What compiler are you using? Clang 3? Can you try it with a different compiler?
|