Forum
Please
Log In
to post a new message or reply to an existing one. If you are not registered, please
register.
NOTE: Some forums may be read-only if you are not currently subscribed to
our technical support services.
|
Subject |
Author |
Date |
|
|
George Ross
|
Feb 19, 2006 - 2:42 AM
|
Hi
i have the ASSERT problem when my application starts caused by CExtControlBar::ProfileBarStateLoad
The program asserts in 3 different states
1. CExtControlBar::ProfileBarStateSerialize LIne 3924 2. CExtControlBar::ProfileBarStateSerialize LIne 3928 CExtControlBar::ProfileBarStateSerialize LIne 3938 Actually throws an exception. Any help i am using ver 2.51 in UNICODE build static library regards George
|
|
|
Technical Support
|
Feb 19, 2006 - 10:49 AM
|
Line 3924 is an ASSERT( FALSE ) assertion inside a catch() statement which rethrows the caught exception. Line 3928 is similar to the previous but inside the outer try/catch statement. Line 3938 is the final ASSERT( bRetVal ) assertion in CExtControlBar::ProfileBarStateSerialize() and it does not throw any exception. Please provide us with the correct location of the code which really throws the exception. Typically CExtControlBar::ProfileBarStateSerialize() is invoked from the CExtControlBar::ProfileBarStateLoad() or CExtControlBar::ProfileBarStateSave() method and it never fails. The state loading algorithm requires all the bars, which are described by serialized data stored in the registry or in a file, have been created. If not, this leads to exceptions and assertions when the state is loaded. For example, it can occur if you changed the identifier of some control bar when developing your app and forgot to clean old serialized data in the registry.
|
|