• 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
attaching Debugger to a running FCP process
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

attaching Debugger to a running FCP process


  • Subject: attaching Debugger to a running FCP process
  • From: Brian Gardner <email@hidden>
  • Date: Sun, 30 Aug 2009 13:11:50 -0700

I'm unable to debug using a custom executable,
and also can not attach to a running FCP 7 or Motion 4 process.
So, the Pro-apps-dev list recommended that I ask this list for advice.
This is my 1st time on the xcode-users list,
so I hope that I'm not intruding.

Here's my problem. I run Final Cut Pro 7. Then from XCode 3.2, 
I perform a Run->Attach to Process->Final Cut Pro
But then, the Debugger exits due to a signal 11.
(See Console output, below at bottom).

I've been developing a FxPlug for Final Cut Pro,
successfully, for several months.
Recently, after upgrading to FCP 7 & Motion 4, which may
not be relevant to my problem, since I probably
also upgraded XCode to 3.1 back then too, and possibly other stuff.
After then, I've been unable to debug my FxPlug with a 
custom executable (FCP 7) because it exits with a status value 45.

So, currently I can't launch FCP as an executable from the debugger, 
nor can I attach to it as a running process.

Next, I upgraded yesterday to Snow Leopard, XCode 3.2,
and FxPlug SDK 1.2.4 -- but problems persisted.
(I'm on an older MacBook Pro 17", so it is Intel based.)

I next tried to isolate the problem, by removing all of my own software plugins,
as well as all 3rd party plugins.
So, I removed everything from /Library/Plug-ins/FxPlug
and ~/Library/Plug-ins/FxPlug
then launched FCP 7, then from XCode 3.2
did the Run->Attach-> to Process->Final Cut Pro.
But the Debugger exited with signal 11
(though, FCP 7 did not exit, it's still running fine).

I tried attaching to Motion 4, as an alternative, but got same results.

The only other thing I can imagine might be 
that some of the 3rd party plugins I purchased were protected
by Pace AP (anti-piracy software). But, those are all legit FxPlug-ins,
and after removing them from the Library directories,
they shouldn't be relevant anyway. And FCP 7 & Motion 4
are running fine ... I just can't launch them from the xcode debugger,
or attach to them as running processes. So, I can't debug my own plugins.

So, I'm a bit stumped and don't know how to proceed.

Can anyone give me a few suggestions?
Or at least an idea on what an exit value 45 is,
and what might cause it?

   -- Brian

[Session started at 2009-08-30 11:21:30 -0700.]
GNU gdb 6.3.50-20050815 (Apple version gdb-1344) (Fri Jul  3 01:19:56 UTC 2009)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-apple-darwin".sharedlibrary apply-load-rules all
Attaching to process 3254.

The Debugger has exited due to signal 11 (SIGSEGV).The Debugger has exited due to signal 11 (SIGSEGV).

 _______________________________________________
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

  • Prev by Date: Re: how do you go back
  • Next by Date: Re: Adding existing svn files to new project
  • Previous by thread: Data detectors (file:line:) for Xcode debug console please!
  • Next by thread: NSOpenpanel in Snow Leopard
  • Index(es):
    • Date
    • Thread