• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: serious problems in GDB / LLDB debugger
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: serious problems in GDB / LLDB debugger


  • Subject: Re: serious problems in GDB / LLDB debugger
  • From: J <email@hidden>
  • Date: Wed, 17 Aug 2011 00:25:31 +0200


hi Lance, 

Of course you're right, I should've given the code for the << operator on Mat4, here it is:

std::ostream & operator << ( std::ostream & s, const Mat4 & v ) { 
static char txt[256];
sprintf( txt, "%g %g %g %g %g %g %g %g %g %g %g %g %g %g %g %g", \
v[ 0 ], v[ 1 ], v[ 2 ], v[ 3 ], \
v[ 4 ], v[ 5 ], v[ 6 ], v[ 7 ], \
v[ 8 ], v[ 9 ], v[ 10 ], v[ 11 ], \
v[ 12 ], v[ 13 ], v[ 14 ], v[ 15 ] );
s << txt;
return s;
}


On Aug 16, 2011, at 11:48 PM, lbland wrote:


hi-

On Aug 16, 2011, at 5:27 PM, J wrote:


The << infix operator doesn't need to print in order of the memory layout? What is the implementation for << in the class?

thanks!-

-lance


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.

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: serious problems in GDB / LLDB debugger
      • From: Quincey Morris <email@hidden>
  • Prev by Date: Re: serious problems in GDB / LLDB debugger
  • Next by Date: Re: serious problems in GDB / LLDB debugger
  • Previous by thread: Re: serious problems in GDB / LLDB debugger
  • Next by thread: Re: serious problems in GDB / LLDB debugger
  • Index(es):
    • Date
    • Thread