I've moved a large GPC project from Mac OSX 10.4 to Snow Leopard (Xcode 3.2, Intel CPU).
Compilation (GNU Pascal 3.4.6u4) is ok, but I can't start debugging from Xcode as I get the following error:
""Exception starting task (/Developer/usr/bin/gdb) ; name: NSInvalidArgumentException, reason: working directory doesn't exist""
With evidence, gdb is looking for the executable in the wrong directory, but I don't know how to workaround that.
Thanks in advance for any help.
-------------------------------------------------------------
Francesco Panasiti
-------------------------------------------------------------
Francesco Panasiti wrote:
I've moved a large GPC project from Mac OSX 10.4 to Snow Leopard (Xcode 3.2, Intel CPU).
Compilation (GNU Pascal 3.4.6u4) is ok, but I can't start debugging from Xcode as I get the following error:
""Exception starting task (/Developer/usr/bin/gdb) ; name: NSInvalidArgumentException, reason: working directory doesn't exist""
With evidence, gdb is looking for the executable in the wrong directory, but I don't know how to workaround that.
Locate the Xcode target executable settings, double-click on it, go to the General tab and choose e.g. "projects directory" for the "Set the working directory to" setting. I assume that will fix it.
Be sure that, when switching the Active build Target, you manually switch the Active Executable, as Xcode doesn't do that automatically for you. I suggest you customize toolbar settings by adding the Active Executable popup menu.
Regards,
Adriaan van Os
It actually fixed the problem.
Thanks so much and regards
Francesco Panasiti
----- Original Message ----- From: "Adriaan van Os" gpc@microbizz.nl To: gpc@gnu.de Sent: Monday, April 26, 2010 4:36 PM Subject: Re: GPC debugging with Snow Leopard/Xcode 3.2
Francesco Panasiti wrote:
I've moved a large GPC project from Mac OSX 10.4 to Snow Leopard (Xcode 3.2, Intel CPU).
Compilation (GNU Pascal 3.4.6u4) is ok, but I can't start debugging from Xcode as I get the following error:
""Exception starting task (/Developer/usr/bin/gdb) ; name: NSInvalidArgumentException, reason: working directory doesn't exist""
With evidence, gdb is looking for the executable in the wrong directory, but I don't know how to workaround that.
Locate the Xcode target executable settings, double-click on it, go to the General tab and choose e.g. "projects directory" for the "Set the working directory to" setting. I assume that will fix it.
Be sure that, when switching the Active build Target, you manually switch the Active Executable, as Xcode doesn't do that automatically for you. I suggest you customize toolbar settings by adding the Active Executable popup menu.
Regards,
Adriaan van Os
-
Adriaan van Os -
Francesco Panasiti