Re: Debugging an AudioUnit in Xcode 2.0

• Subject: Re: Debugging an AudioUnit in Xcode 2.0
• From: Pavol Markovič <email@hidden>
• Date: Wed, 30 Nov 2005 08:41:50 +0100
• Delivered-to: email@hidden
• Delivered-to: email@hidden
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:in-reply-to:references:mime-version:content-type:message-id:content-transfer-encoding:cc:from:subject:date:to:x-mailer; b=FlK6r4PjvIXfDKgED80NX0jV8vpIon2T+vBTzrjtfggHbnbE4EfzaHx9ySuqqlGLzaXtRDONfz5/RlLnqvFkxOeTeDnq1qDW/XOXvcGSgh2Inl+HnfaFUojzcxmLHlFAAY/3L/fqsNYvKFEgETpuIe/+cg9io+TPqXjW94TaRuM=

However, they are when it's started without a debugger. They all echo the following (snippet):

code 4, error number 0 (Symbol not found: __FSOpenForkWithCatalogInfo
Referenced from: /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/ Versions/A/DesktopServicesPriv
Expected in: /System/Library/Frameworks/CoreServices.framework/Versions/A/ CoreServices_debug
)

Hm, looking at this output I'd guess that maybe you did specify a binary image suffix ("_debug") in your XCode settings somewhere.
Seems like this is set so it tries to load the debug version of CoreServices - which for some reason doesn't implement __FSOpenForkWithCatalogInfo.

Looks like some symbols are missing in _debug frameworks.

PM

On Nov 29, 2005, at 6:42 PM, Jim Ingham wrote:

Interesting... The _debug versions of the system libraries have a lot of asserts that are supposed to catch various programming errors. That Logic or some component below it is tripping over one of the asserts is worth filing a bug over. Either there's a problem with Logic (or whoever is actually raising the assert) or with the assert itself. Anyway, that's not a tools problem.

Jim

On Nov 29, 2005, at 1:22 AM, Mikael Hillborg wrote:

Jim Ingham wrote:

Try breaking on "abort" and "exit" and see where it's exiting.  That
might give you some better sense of what is going on?

You can eliminate environment variable effects by running the
program, and doing "show env" from gdb.  Then try running the app and
attaching to it (you can do this from the GUI in Xcode 2.2.)  You can
then do "show env" and compare the two.

Anyway, as long as you don't need to debug the app startup, you can
use "attaching" to the already running app as a workaround.

Jim

I'll try. There's a work around though. That is to open the Executable
inspector in Xcode, go to the General tab and select "Use 'no' suffix
when loading frameworks". Then the ordinary system libraries, and not
the debug versions, will be loaded and it'll work. The debug system
libraries which have the suffix _debug seem to create a problem
causing the hosts to exit (in both Xcode 2.2 and 2.0).

Mike

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

This email sent to email@hidden

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

• Prev by Date: RE: Debugging an AudioUnit in Xcode 2.0
• Next by Date: Link problem with custom static library
• Previous by thread: Re: Debugging an AudioUnit in Xcode 2.0
• Next by thread: XFree86 and Fortran in OS 10.3
• Index(es):
  • Date
  • Thread