I am using the Leaks instrument, and it has identified a bunch of 32 and 48 byte "Malloc" leaks. I would like to see a hex dump of some (or all) of those areas. I think if I can see what is in them I can get a better idea about what is triggering the leak.
I'm pretty sure it is a real leak.
What is the easy way to do this? Can it be done inside instruments, or do I need to run my app under instruments and also attach via lldb and hexdump from lldb? (can I attach lldb and instruments at the same time?)
If it matters I'm debugging an iPadOS app, and it is written in Swift plus ObjC, plus ObjC++, oh, and some straight C++.
theonetruestripes
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
United States
Post
Replies
Boosts
Views
Activity
I have an application where I drive a laser cutter. I need to generate vectors. I currently use the "old" TextKit to generate text fragments full of glyphs and NSBezierPath's append(withCGGlyph glyph: CGGlyph, in font: NSFont) to get a BezierPath that I then convert to laser cutter vectors.
For example:
With TextKit2 it looks like it is a major goal to avoid the complexities of Glyphs, which is cool. However is there some API (new, or something old that I missed) that can get me from the text in the TextFragment to a BezierPath? I would hate to be unable to make the jump to TextKit2 (both because TextKit2 looks easier to deal with, and because I'm sure TextKit1 is going to go away...)