• 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
Getting otx or Mach-O-Scope to work
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Getting otx or Mach-O-Scope to work


  • Subject: Getting otx or Mach-O-Scope to work
  • From: Jens Alfke <email@hidden>
  • Date: Sun, 15 Jan 2012 12:58:28 -0800

The ‘otx’ tool [fancy extension of otool], and the ‘Mach-O-Scope’ app that uses it, have both been mentioned here recently. I’d love to use them, but I can’t get either to work, and searching hasn’t turned up any relevant info.

First off, I have a pretty typical setup — MacBook Pro 2010, OS X 10.7.2, Xcode 4.2.1.

If I download and run the latest otx (0.16b), it complains that the executable in any app or framework I’ve built is “not a Mach-O file”. It does work on system tools / frameworks and on itself. Is it somehow incompatible with binaries built by the linker in Xcode 4.2?

Mach-O-Scope launches but nothing happens when I open anything. Turns out the bundled copy of otx contained in its repo won’t run — if I launch it from a shell, it immediately crashes with an uncaught exception :

> $ ./otx otx
> 2012-01-15 12:54:54.939 otx[25872:303] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'launch path not accessible'
> *** Call stack at first throw:
> (
> 	0   CoreFoundation                      0x99181d87 __raiseError + 231
> 	1   libobjc.A.dylib                     0x91e85149 objc_exception_throw + 155
> 	2   CoreFoundation                      0x990e9619 +[NSException raise:format:arguments:] + 137
> 	3   CoreFoundation                      0x990e9589 +[NSException raise:format:] + 57
> 	4   Foundation                          0x99406731 -[NSConcreteTask launchWithDictionary:] + 506
> 	5   Foundation                          0x99406532 -[NSConcreteTask launch] + 40
> 	6   otx                                 0x000243fb -[NSObject(SysUtils) checkOtool:] + 203
> 	7   otx                                 0x00002d49 -[CLIController processFile] + 73
> 	8   otx                                 0x00003ef3 main + 147
> 	9   otx                                 0x000029cb _start + 209
> 	10  otx                                 0x000028f9 start + 41
> 	11  ???                                 0x00000002 0x0 + 2
> )
> Trace/BPT trap


Anyone have any idea what’s going wrong here? I realize I could check out the source to otx and debug it myself, but I’ve already spent more time on this than I should, and I can’t believe I’ve got some uniquely weird setup...

—Jens _______________________________________________
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: Getting otx or Mach-O-Scope to work
      • From: Jens Alfke <email@hidden>
  • Prev by Date: Can't symbolicate crash reports
  • Next by Date: Framework copy
  • Previous by thread: Re: Can't symbolicate crash reports
  • Next by thread: Re: Getting otx or Mach-O-Scope to work
  • Index(es):
    • Date
    • Thread