Re: Help - can't debug plugins anymore
Re: Help - can't debug plugins anymore
- Subject: Re: Help - can't debug plugins anymore
- From: "infinite labs" <email@hidden>
- Date: Sun, 12 Oct 2008 13:51:39 +0200
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.
- ∞
_______________________________________________
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