Closed
Bug 210045
Opened 22 years ago
Closed 22 years ago
oeICalImpl doesn't initialize m_alarmtimer
Categories
(Calendar :: Internal Components, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: timeless, Assigned: timeless)
Details
xpcshell:
const C=Components.classes,I=Components.interfaces;
for (a in C) try {C[a].createInstance(I.nsIInputStream); print(a)}catch(e){}
oeICalImpl::~oeICalImpl() line 277 + 16 bytes
oeICalImpl::`scalar deleting destructor'(unsigned int 1) + 15 bytes
oeICalImpl::Release(oeICalImpl * const 0x03494ec0) line 299 + 106 bytes
oeICalImplConstructor(nsISupports * 0x00000000, const nsID & {...}, void * *
0x0012e794) line 47 + 154 bytes
m_alarmtimer->GetDelay( &delay );
+ m_alarmtimer 0xcdcdcdcd
hrm, my file was out of sync
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
|
||
Comment 2•19 years ago
|
||
Mass move of libxpical bugs to the Internal Components, per ctalbert.
Component: libxpical → Internal Components
|
||
Comment 3•19 years ago
|
||
The bugspam monkeys have been set free and are feeding on Calendar :: Internal Components. Be afraid for your sanity!
QA Contact: gurganbl → base
You need to log in
before you can comment on or make changes to this bug.
Description
•