Closed
Bug 17021
Opened 25 years ago
Closed 25 years ago
Asseration problem involving ns_ReadDesc()
Categories
(Core :: XPCOM, defect, P3)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: ppandit, Assigned: dveditz)
Details
Did a depend build today on Windows NT 4.0
Started mozilla.exe and got the following problem before any windows are
displayed.
I can't get past this problem even after pressing F5.
Press F5 enough times and my system hangs.
NTDLL! DbgBreakPoint@0 address 0x77f76148
PR_Assert(const char * 0x0028dab8, const char * 0x0028da94, int 840) line 449
nr_ReadDesc(_regfile * 0x00c05a40, long 2, _desc * 0x0012f520) line 840 + 38
bytes
NR_RegSetEntry(void * 0x00c6b9f0, long 2, char * 0x0012f5e4, unsigned short 18,
void * 0x0012f5b0, unsigned long 4) line 3185 + 17 bytes
nsRegistry::SetInt(nsRegistry * const 0x00c6bd50, unsigned int 2, const char *
0x0012f5e4, int 1242856) line 632 + 28 bytes
NSRegisterSelf(nsISupports * 0x00c04980, const char * 0x00c6a380) line 72 + 25
bytes
nsNativeComponentLoader::SelfRegisterDll(nsDll * 0x00c053d0, const char *
0x00c6a380) line 515 + 14 bytes
nsNativeComponentLoader::AutoRegisterComponent(nsNativeComponentLoader * const
0x00c04110, int 0, nsIFileSpec * 0x00c6a060, int * 0x0012fccc) line 855 + 19
bytes
nsNativeComponentLoader::RegisterComponentsInDir(nsNativeComponentLoader * const
0x00c04110, int 0, nsIFileSpec * 0x00c6a8b0) line 321 + 24 bytes
nsNativeComponentLoader::AutoRegisterComponents(nsNativeComponentLoader * const
0x00c04110, int 0, nsIFileSpec * 0x00c6a8b0) line 260 + 20 bytes
nsComponentManagerImpl::AutoRegister(nsComponentManagerImpl * const 0x00c04620,
int 0, nsIFileSpec * 0x00000000) line 2003 + 31 bytes
nsComponentManager::AutoRegister(int 0, nsIFileSpec * 0x00000000) line 197
NS_AutoregisterComponents() line 95 + 10 bytes
NS_SetupRegistry_1() line 120
main1(int 1, char * * 0x00c049c0) line 505
main(int 1, char * * 0x00c049c0) line 694 + 13 bytes
mainCRTStartup() line 338 + 17 bytes
KERNEL32! BaseProcessStart@4 + 64 bytes
Updated•25 years ago
|
Assignee: don → dp
Component: Browser-General → XPCOM Registry
Updated•25 years ago
|
Assignee: dp → dveditz
Did another pull and rebuild - no longer seeing the problem
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Comment 2•25 years ago
|
||
I guess reopen this if the problem comes back. This sort of thing could be due
to corruption in the component.reg file so it might be nice to save that file
and pass it along (although the chances of figuring out *what* corrupted it are
slim). Then try deleting that file and restarting.
You need to log in
before you can comment on or make changes to this bug.
Description
•