[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debugging an AudioUnit in Xcode 2.0

Subject: Re: Debugging an AudioUnit in Xcode 2.0
From: Jim Ingham <email@hidden>
Date: Mon, 28 Nov 2005 11:21:22 -0800
Delivered-to: email@hidden
Delivered-to: email@hidden

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

On Nov 23, 2005, at 2:23 PM, Mikael Hillborg wrote:

Pavol Markovic wrote:
Maybe output from Xcode's gdb console can bring some enlightenment here.
Here's the output with Logic Pro 7 as the host. It seems to throw an
exception, don't ask me why, it works fine if it's started with the
AudioUnit, but without the GDB debugger:
(gdb) run [Switching to process 431 local thread 0xf03] Running… 2005-11-23 23:10:10.214 Logic Pro[431] CFLog (0): Assertions enabled 2005-11-23 23:10:10.593 auval[439] CFLog (0): Assertions enabled 2005-11-23 23:10:10.853 auval[440] CFLog (0): Assertions enabled 2005-11-23 23:10:12.005 Logic Pro[431]: DebugAssert: HIToolbox: ResolveLinkedMenuItem( &menuData, (MenuItemIndex*) &item ) exception_DeleteMenuItem_ItemOutOfRange [Menus/Source/MenuItems.cp: 802] 2005-11-23 23:10:12.279 Logic Pro[431]: DebugAssert: HIToolbox: ResolveLinkedMenuItem( &menuData, (MenuItemIndex*) &item ) exception_DeleteMenuItem_ItemOutOfRange [Menus/Source/MenuItems.cp: 802] (gdb)

And here's the output with Metro 6.0.8 as the host. No exceptions here, but the same problem (the host never starts):

(gdb) run [Switching to process 417 local thread 0xf03] Running… 2005-11-23 23:08:34.011 Metro G4[417] CFLog (0): Assertions enabled 2005-11-23 23:08:36.090 Metro G4[417]: DebugAssert: ATS: Using old glyphs cache path[Glyphs/ATSGlyph.c:455] 2005-11-23 23:08:36.310 Metro G4[417]: DebugAssert: ATS: Using old glyphs cache path[Glyphs/ATSGlyph.c:455] (gdb)

If I start these hosts by double clicking on them, the usual way, then they start and the AudioUnit can also be run without any problems. It also passes the auval. Maybe this is a question I should ask on the CoreAudio list instead, but the problem really seems to be with GDB and/or Xcode. Debug info is generated and all optimizations are switched off (very debuggable).
/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

This email sent to email@hidden

Follow-Ups:
- RE: Debugging an AudioUnit in Xcode 2.0
  - From: "Mikael Hillborg" <email@hidden>

References:
	>RE: Debugging an AudioUnit in Xcode 2.0 (From: "Mikael Hillborg" <email@hidden>)

Prev by Date: Re: Three Level Dependencies between xcode projects still fails in XCode 2.2
Next by Date: Re: /Library/Caches/com.apple.Xcode.<UID> is huge!
Previous by thread: RE: Debugging an AudioUnit in Xcode 2.0
Next by thread: RE: Debugging an AudioUnit in Xcode 2.0
Index(es):
- Date
- Thread

Home