Closed Bug 202476 Opened 23 years ago Closed 17 years ago

debugging mozilla in VC.net can cause "user shell folders" reg key to be hosed

Categories

(Testing :: General, defect, P5)

x86
Windows XP
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: teilo+bugzilla, Unassigned)

Details

Attachments

(1 file)

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705) Build Identifier: 1,4a CVS (Wed Mar 26 12:36:47 2003) Under some specific circumstances (yet to be established) when debugging a cvs build of mozilla with MS VC.Net certain keys under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders and their related keys under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders become corrupted and set to be paths under the Windows folder. This does not happen when running mozilla normally or debugging other programms in VC. Reproducible: Sometimes Steps to Reproduce: 1. Build a debug version of mozilla with a breakpoint entered into the code somewhere (__debugbreak()) 2. start mozilla and run till it hits the break point 3. Launch the VC debugger when prompted 4. stop the debugging in VC (and terminate process) 5. restart the debugging by launching app in VC 6. goto 4 Actual Results: Sometimes when executing step 5 I no longer get the profile manger dialog. Whenever this happens certain keys under the previously mentioned roots have been changed (Desktop, AppData, Favourites) Expected Results: the registry values should be left unchanged. Not sure what is causing this. I'll try and run with regmon ( http://www.sysinternals.com/ntw2k/source/regmon.shtml ) and see who the culprit is (mozilla, VC, OS)
Priority: -- → P5
WTF is moz even attempting by *writing* under HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\ and writing to HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Favorites During the capture of this log the keys didn't become hosed but it is now easy to see why they might. I'm very scared about whats going on with the mount points.
not blocking development severity -> critical
Assignee: asa → general
Severity: blocker → critical
Product: Browser → Seamonkey
Assignee: general → nobody
Product: SeaMonkey → Testing
QA Contact: asa → general
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: