Re: Different GDB than the native processors.
Re: Different GDB than the native processors.
- Subject: Re: Different GDB than the native processors.
- From: Nick Lott <email@hidden>
- Date: Sat, 20 Aug 2005 23:35:43 +1200
Is there anyway to get around this?
What hacks would be required to
- make the xcode debugger talk to a remote host
- issue "continue" instead of "run"
- recognize the elf file as an executable instead of "No Launchable
executable at path"
- get the gui to resync with gdb after entering manual commands in
the console
I managed to get it to connect (to my JTAG via avarice)by pointing
xcode to some ppc executable app and then jumping into the console
and issuing the following
"cd /projectdir/"
"file main.elf"
"target remote localhost:4242"
how can I get the gui to reflect these changes? and show the source
code etc.
Any hints whatsoever very much appreciated.
Cheers,
nick.
On Fri, 19 Aug 2005 17:40:50 -0700, Jim Ingham <email@hidden>
wrote:
That will get Xcode to run another debugger, but that only gets you a
little way.
Xcode is not going to issue commands that you need (like "target
remote") and is probably going to issue commands you don't want (like
calling dlopen in your target program to insert its debugging
library). It is going to assume your target is a true asynchronous
target, which it most likely isn't, so interrupting execution won't
work...
Dunno how much hacking you are willing to do here, but you may need
to do more than somewhat...
Jim
_______________________________________________
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