RESOLVED INVALID 46037
Cannot debug WebKit in VC++ 2005 Express
https://bugs.webkit.org/show_bug.cgi?id=46037
Summary Cannot debug WebKit in VC++ 2005 Express
ljgeneral
Reported 2010-09-18 09:03:14 PDT
After building these codes in Visual C++ 2005 Express successfully, i want to debug them step by step in Visual C++ 2005 Express.Firstly I execute the script 'webkit/webkittools/scripts/run-safari --debug' in cygwin and get the following output: "Your copy of safari is missing important software resources. Please reinstall Safari" then I try to download the latest version from web and reinstall it, but the error still exists. I try the same steps in another computer.it works fine. I do not know why. the operation system and the environment are the same. I launch safari in another computer using script 'run-safari --debug', then i open Visual C++ 2005 Express and set debug attach to safari process. and i also set some break points in the codes. but it does not work. how can i do if i want to debug these codes step by step? thank you very much.
Attachments
Alexey Proskuryakov
Comment 1 2010-09-19 11:53:59 PDT
Isn't there a debug-safari script for that? Not sure if it's expected to work on Windows though.
Adam Roben (:aroben)
Comment 2 2010-09-20 06:37:31 PDT
(In reply to comment #0) > After building these codes in Visual C++ 2005 Express successfully, i want to debug them step by step in Visual C++ 2005 Express.Firstly I execute the script 'webkit/webkittools/scripts/run-safari --debug' in cygwin and get the following output: > "Your copy of safari is missing important software resources. Please reinstall Safari" "run-safari --debug" means "run Safari using the Debug version of WebKit that I've built". If you did a Release build instead of a Debug build, it won't work. (In reply to comment #1) > Isn't there a debug-safari script for that? Not sure if it's expected to work on Windows though. It is expected to work on Windows. Another option is to follow the instructions here: http://webkit.org/building/debug.html
Note You need to log in before you can comment on or make changes to this bug.