Bug 32297

Summary: WebCore source level debugging on Windows not reliable in some cases
Product: WebKit Reporter: Steve Falkenburg <sfalken>
Component: WebKit Misc.Assignee: Steve Falkenburg <sfalken>
Status: RESOLVED FIXED    
Severity: Normal CC: aroben, sfalken, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Windows 7   
Attachments:
Description Flags
Add ProgramDataBaseFileName to vsprops aroben: review+

Steve Falkenburg
Reported 2009-12-08 16:24:58 PST
WebCore on Windows links as a static library. Later in the build process, this static library is linked into WebKit.dll. The WebCore build generates its symbolic information into a vc80.pdb file sitting in the WebCore obj directory. Depending on how to components are built, this pdb can be lost. This can result in an inability to source level debug the WebCore code. A similar issue is discussed here: http://stackoverflow.com/questions/253727/vc80-pdb-how-do-i-make-it-go-away-and-never-bother-me-again The fix is to use a more applicable name for vc80.pdb, and to generate it into a folder alongside WebKit.lib. As long as the pdb is carried along the build process with WebKit.lib, symbols will be available for debugging.
Attachments
Add ProgramDataBaseFileName to vsprops (1.52 KB, patch)
2009-12-08 16:46 PST, Steve Falkenburg 		aroben: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Steve Falkenburg
Comment 1 2009-12-08 16:46:06 PST
Created attachment 44498 [details] Add ProgramDataBaseFileName to vsprops
WebKit Review Bot
Comment 2 2009-12-08 16:50:30 PST
style-queue ran check-webkit-style on attachment 44498 [details] without any errors.
Adam Roben (:aroben)
Comment 3 2009-12-08 16:55:00 PST
Comment on attachment 44498 [details] Add ProgramDataBaseFileName to vsprops r=me
Steve Falkenburg
Comment 4 2009-12-08 17:02:16 PST
Fixed in http://trac.webkit.org/changeset/51881
Note You need to log in before you can comment on or make changes to this bug.