Debugging in Xcode using a custom executable
Is there a way to debug WebKit using a custom executable in Xcode? I opened a new project, created a custom executable with / Applications/Safari.app as the executable path and with the environment variable DYLD_FRAMEWORK_PATH set to the build destination of WebKit. Source-level debugging seems to work only for the objective-C parts, though. The C++ parts show as "??" in the call stack and of course I don't get their source code. Any suggestions? -- Mitz Pettel
On Jun 16, 2005, at 2:44 PM, Mitz Pettel wrote:
Is there a way to debug WebKit using a custom executable in Xcode?
I opened a new project, created a custom executable with / Applications/Safari.app as the executable path and with the environment variable DYLD_FRAMEWORK_PATH set to the build destination of WebKit.
Source-level debugging seems to work only for the objective-C parts, though. The C++ parts show as "??" in the call stack and of course I don't get their source code.
Any suggestions?
Maybe this is too obvious, but... did you do a Development or Deployment build of WebKit? Regards, Maciej
On Jun 20, 2005, at 7:49 AM, Maciej Stachowiak wrote:
On Jun 16, 2005, at 2:44 PM, Mitz Pettel wrote:
Is there a way to debug WebKit using a custom executable in Xcode?
I opened a new project, created a custom executable with / Applications/Safari.app as the executable path and with the environment variable DYLD_FRAMEWORK_PATH set to the build destination of WebKit.
Source-level debugging seems to work only for the objective-C parts, though. The C++ parts show as "??" in the call stack and of course I don't get their source code.
Any suggestions?
Maybe this is too obvious, but... did you do a Development or Deployment build of WebKit?
I did a Development build. The problem turned out to be Xcode's (too-) lazy symbol loading and I solved it by choosing Debug > Tools > Shared Libraries and changing the Starting Level for WebKit and WebCore to All. -- Mitz Pettel
participants (2)
-
Maciej Stachowiak
-
Mitz Pettel