> On 6 Jun 2015, at 00:07, Kate Stone <[email protected]> wrote: > > Suggestions can always be filed via http://bugreport.apple.com > <http://bugreport.apple.com/> and are more likely to get proper consideration > by the appropriate team than conversations on a mailing list. In this case > I’ve gone ahead and logged the request, but it’s always safest to log > suggestions yourself so there’s a way for engineering to ask clarifying > questions.
It used to work fine in XCode 3, they changed it, one would assume for a reason (not that I or anyone I’ve asked can work out what that reason was), I see no point wasting my time posting suggestions when, a) it’s been deliberately changed (e.g. not a bug or a first instance of a feature) , b) the functionality is obvious, anyone with any experience working on low level code should know what is required of a debugger when it comes to displaying memory contents and addresses, the industry has been doing it since the 1950’s, why now should we have to point out the obvious to Apple? Seems beyond belief that they would cripple a useful feature and make it all but worthless, but Apple knows best! I’ll just write some logging code to dump memory when I need to and forget about using the debugger for it. Cheers Dave > > Kate Stone [email protected] <mailto:[email protected]> > Xcode Runtime Analysis Tools > >> On Jun 5, 2015, at 3:58 PM, Tony Scaminaci <[email protected] >> <mailto:[email protected]>> wrote: >> >> I too find later versions of Xcode lacking intuitive functionality. I still >> have CodeWarrior on an old Quadra 950 and have to agree that CW was the gold >> standard IDE. It does seem that early Xcode versions were mimicking CW but >> over the years, the Xcode IDE has become harder to use. Too many features >> are being moved around. It took me a while to figure out how to turn off >> support for PPC in older apps I was updating. In a couple of cases, it's >> actually been easier to start a new project from scratch rather than fiddle >> with all the existing settings. >> >> Back on topic, clicking in the memory window to toggle between hex and >> decimal values is not intuitive at all. CW had that feature in a pull-down >> menu where it was easily found instead of a hidden trick we need Apple to >> tell us about. >> >> Sent from Yahoo Mail for iPhone <https://yho.com/footer0> >> >> At Jun 5, 2015, 5:44:29 AM, Dave wrote: >> Hi, >> >> Thanks I’ll have a play around but it’s still very hard to use compared to >> other Debuggers I’ve used. >> >> I just checked on an old machine running XCode 3, the Memory display >> handling is so much better. I thought I remember being able to do all the >> things I wanted but couldn’t remember which App it was in. I think the XCode >> 3 way of doing things was copied from CodeWarrior which pretty much set the >> standard for Mac based development back in the day. >> >> Cheers >> Dave >> >>> On 4 Jun 2015, at 12:53, Dave <[email protected] <javascript:return>> >>> wrote: >>> >> >> Hi, >> >> Thanks viewing it in a separate window makes things a little easier, but is >> there a way to get the addresses on the left to display in Hex too? Also is >> there a way to specify a type that “myBufferPtr” points to as something >> other than bytes? e.g. Int64, 32, 16, 8 etc and in Big/Little Endian? >> >> All the Best >> Dave >> >>> On 3 Jun 2015, at 17:17, Steve Mills <[email protected] <javascript:return>> >>> wrote: >>> >>> On Jun 03, 2015, at 10:40 AM, Dave <[email protected] >>> <javascript:return>> wrote: >>> >>>> How can I View a Raw Buffer in the Debugger? I’ve tried right clicking and >>>> selecting View Raw Memory, but firstly this Changes the Source code >>>> display to Show the Memory instead if using the Value Inspection pane, >>>> secondly, it displays the addresses in decimal instead of hex and thirdly >>>> I don’t think its displaying the correct data anyway. >>>> >>>> I have this code: >>>> >>>> void*myBufferPtr; >>>> >>>> myBufferPtr = malloc(myTotalLength * sizeof(NSUInteger)); >>>> if (myBufferPtr == NULL) >>>> returnnil; >>>> >>>> [self getIndexes:myBufferPtr]; >>>> >>>> And I just want to look at the data pointed to by myBufferPtr. >>> >>> >>> Right-click the variable myBufferPtr and choose View Memory of >>> "*myBufferPtr". Hold down option-shift as you choose that menu item to open >>> the navigation chooser, then you can double-click the "open in a new >>> window" dealy bob so it won't replace your source code view. >>> >>> Steve >>> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Xcode-users mailing list ([email protected] <javascript:return>) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/xcode-users/dave%40looktowindward.com >> >> <https://lists.apple.com/mailman/options/xcode-users/dave%40looktowindward.com> >> >> This email sent to [email protected] <mailto:[email protected]> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Xcode-users mailing list ([email protected] >> <mailto:[email protected]>) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/xcode-users/katherine_stone%40apple.com >> >> <https://lists.apple.com/mailman/options/xcode-users/katherine_stone%40apple.com> >> >> This email sent to [email protected] >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
