• 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
Re: Help - can't debug plugins anymore
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Help - can't debug plugins anymore


  • Subject: Re: Help - can't debug plugins anymore
  • From: Emanuele Vulcano <email@hidden>
  • Date: Mon, 13 Oct 2008 07:30:05 +0200

That is, however, a classical symptom of having modified a GDB-traced app through mach_inject. The error in that case occurs in a secondary thread, the one m_i creates in the app to run the injected code on. IMs do not use mach_inject, but some apps (like my own PS) might. If the above seems to be the case, try disabling login items and launch agents.

 - ev

Il giorno 12/ott/08, alle ore 17:53, "Mark Munz" <email@hidden> ha scritto:

I have already tried removing all the Input Managers and GDB still
fails to debug under the same circumstance. It works fine for
debugging a full app, but if I have a project where a host app loads
my plugin, it chokes while launching the host app.

I listed the two IM bundles I had previously just for thoroughness.
I am not using PlugSuit as far as I can tell.

Thanks.


On Sun, Oct 12, 2008 at 4:51 AM, infinite labs <me@infinite- labs.net> wrote:
On Sun, Oct 12, 2008 at 12:47 AM, Mark Munz <email@hidden> wrote:
GDB seems to have crapped out when debugging using another host app.

Running Xcode 3.1

I keep getting an "Cannot access memory at address 0x4"

Past folks pointed to kext and IM as the source, but I've ruled out IM.

The only non-Apple kext I have installed is vmware (v2.0).
I have 1PasswdIM & Menu Extra Enabler Input Managers, but removed both
w/o change.


I can debug a full application -- that I build-- just fine, but if I
build and debug my plug-in and (running another app as the host), I'm
constantly getting the above error message. I'd really like to rejoin
the 21st century and debug my plugins inside of Xcode instead of going
to the very slow NSLog message based approach.


Anyone have any ideas as other potential causes to this problem?

Er, that would be my fault.
If you use PlugSuit or another application enhancer, disable it before
debugging. The next version of PS will refrain from injecting into
processes that have a GDB instance as their parent, if I can figure
out how to figure that out.


- ∞




-- Mark Munz unmarked software http://www.unmarked.com/
_______________________________________________
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: Help - can't debug plugins anymore
      • From: "Mark Munz" <email@hidden>
References: 
 >Help - can't debug plugins anymore (From: "Mark Munz" <email@hidden>)
 >Re: Help - can't debug plugins anymore (From: "infinite labs" <email@hidden>)
 >Re: Help - can't debug plugins anymore (From: "Mark Munz" <email@hidden>)

  • Prev by Date: Re: Help - XCode '<unknown>' platform error
  • Next by Date: Re: Help - can't debug plugins anymore
  • Previous by thread: Re: Help - can't debug plugins anymore
  • Next by thread: Re: Help - can't debug plugins anymore
  • Index(es):
    • Date
    • Thread