Site Map / Register

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.

Forums » Prof-UIS General Discussion » CExtControlBar that crash...or is miss used

Subject	Author	Date
CExtControlBar that crash...or is miss used	Ionut Ceausu	Mar 18, 2005 - 10:37 AM
I have a crash: <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p> </o:p> The stack is the following one and if I take a look in the stack I observe that at a moment an assert is fired (but no window is displayed). The assert contains the following text : <o:p></o:p> .Program: ...P_MS_Extens<o:p></o:p> ion\VoIPEngine\MediaServ<o:p></o:p> er\IxView\Debug\IxView.e<o:p></o:p> xe.File: D:\Prof-UIS\Src<o:p></o:p> \extcontrolbar.cpp.Line:<o:p></o:p> 18935..For information <o:p></o:p> on how your program can <o:p></o:p> cause an assertion.failu<o:p></o:p> re, see the Visual C++ d<o:p></o:p> ocumentation on asserts.<o:p></o:p> ..(Press Retry to debug <o:p></o:p> the application)...... <o:p> </o:p> Sorry for the layout is taken out from memory debug window After that...I receive an access violation and that is it. NTDLL! 77f813b1()<o:p></o:p> _CrtDbgReport(int 2, const char * 0x008c4fe0, int 18935, const char * 0x00000000, const char * 0x00000000) line 353<o:p></o:p> AfxAssertFailedLine(const char * 0x008c4fe0, int 18935) line 39 + 20 bytes<o:p></o:p> PROFUIS227MD! 005d4afe()<o:p></o:p> PROFUIS227MD! 005d4837()<o:p></o:p> PROFUIS227MD! 005d4641()<o:p></o:p> PROFUIS227MD! 005c1f1b()<o:p></o:p> PROFUIS227MD! 005bd7a6()<o:p></o:p> PROFUIS227MD! 005b680b()<o:p></o:p> CWnd::OnWndMsg(unsigned int 31, unsigned int 0, long 0, long * 0x0012ac64) line 1825<o:p></o:p> CWnd::WindowProc(unsigned int 31, unsigned int 0, long 0) line 1585 + 30 bytes<o:p></o:p> CControlBar::WindowProc(unsigned int 31, unsigned int 0, long 0) line 480 + 20 bytes<o:p></o:p> PROFUIS227MD! 005b3e83()<o:p></o:p> CIxControlBar::WindowProc(unsigned int 31, unsigned int 0, long 0) line 155 + 23 bytes<o:p></o:p> AfxCallWndProc(CWnd * 0x034803d0 {CIxControlBar hWnd=???}, HWND__ * 0x00040994, unsigned int 31, unsigned int 0, long 0) line 215 + 26 bytes<o:p></o:p> AfxWndProc(HWND__ * 0x00040994, unsigned int 31, unsigned int 0, long 0) line 368<o:p></o:p> AfxWndProcBase(HWND__ * 0x00040994, unsigned int 31, unsigned int 0, long 0) line 220 + 21 bytes<o:p></o:p> USER32! 77e3a420()<o:p></o:p> USER32! 77e16381()<o:p></o:p> USER32! 77e17361()<o:p></o:p> USER32! 77e33458()<o:p></o:p> USER32! 77e441d4()<o:p></o:p> USER32! 77e34110()<o:p></o:p> USER32! 77e344ac()<o:p></o:p> USER32! 77e3399f()<o:p></o:p> USER32! 77e34237()<o:p></o:p> USER32! 77e333d0()<o:p></o:p> __crtMessageBoxA(const char * 0x0012b448, const char * 0x102579a0 `string’, unsigned int 73746) line 65<o:p></o:p> CrtMessageWindow(int 2, const char * 0x008c4fe0, const char * 0x0012c57c, const char * 0x00000000, const char * 0x0012e5a0) line 520 + 22 bytes<o:p></o:p> _CrtDbgReport(int 2, const char * 0x008c4fe0, int 18935, const char * 0x00000000, const char * 0x00000000) line 419 + 76 bytes<o:p></o:p> AfxAssertFailedLine(const char * 0x008c4fe0, int 18935) line 39 + 20 bytes<o:p></o:p> PROFUIS227MD! 005d4afe()<o:p></o:p> PROFUIS227MD! 005d4837()<o:p></o:p> PROFUIS227MD! 005d4641()<o:p></o:p> PROFUIS227MD! 005c1f1b()<o:p></o:p> PROFUIS227MD! 005bdde2()<o:p></o:p> PROFUIS227MD! 005b6a13()<o:p></o:p> PROFUIS227MD! 005bd18c()<o:p></o:p> PROFUIS227MD! 005b7657()<o:p></o:p> CWnd::OnWndMsg(unsigned int 513, unsigned int 1, long -1179468, long * 0x0012fa4c) line 1964<o:p></o:p> CWnd::WindowProc(unsigned int 513, unsigned int 1, long -1179468) line 1585 + 30 bytes<o:p></o:p> CControlBar::WindowProc(unsigned int 513, unsigned int 1, long -1179468) line 480 + 20 bytes<o:p></o:p> PROFUIS227MD! 005b3e83()<o:p></o:p> CIxControlBar::WindowProc(unsigned int 513, unsigned int 1, long -1179468) line 155 + 23 bytes<o:p></o:p> AfxCallWndProc(CWnd * 0x034803d0 {CIxControlBar hWnd=???}, HWND__ * 0x00040994, unsigned int 513, unsigned int 1, long -1179468) line 215 + 26 bytes<o:p></o:p> AfxWndProc(HWND__ * 0x00040994, unsigned int 513, unsigned int 1, long -1179468) line 368<o:p></o:p> AfxWndProcBase(HWND__ * 0x00040994, unsigned int 513, unsigned int 1, long -1179468) line 220 + 21 bytes<o:p></o:p> USER32! 77e3a420()<o:p></o:p> USER32! 77e14605()<o:p></o:p> USER32! 77e1a7ba()<o:p></o:p> USER32! 77e2f49d()<o:p></o:p> CWnd::IsDialogMessageA(tagMSG * 0x00465e98 {msg=0x0000c12a wp=0x00000011 lp=0x00040994}) line 182<o:p></o:p> CWnd::PreTranslateInput(tagMSG * 0x00465e98 {msg=0x0000c12a wp=0x00000011 lp=0x00040994}) line 3424<o:p></o:p> PROFUIS227MD! 005cf13f()<o:p></o:p> CIxControlBar::PreTranslateMessage(tagMSG * 0x00465e98 {msg=0x0000c12a wp=0x00000011 lp=0x00040994}) line 73 + 15 bytes<o:p></o:p> CWnd::WalkPreTranslateTree(HWND__ * 0x0022045c, tagMSG * 0x00465e98 {msg=0x0000c12a wp=0x00000011 lp=0x00040994}) line 2667 + 18 bytes<o:p></o:p> CWinThread::PreTranslateMessage(tagMSG * 0x00465e98 {msg=0x0000c12a wp=0x00000011 lp=0x00040994}) line 672 + 18 bytes<o:p></o:p> CWinThread::PumpMessage() line 848 + 30 bytes<o:p></o:p> CWinThread::Run() line 487 + 11 bytes<o:p></o:p> CWinApp::Run() line 400<o:p></o:p> AfxWinMain(HINSTANCE__ * 0x00400000, HINSTANCE__ * 0x00000000, char * 0x001436a8, int 1) line 49 + 11 bytes<o:p></o:p> WinMain(HINSTANCE__ * 0x00400000, HINSTANCE__ * 0x00000000, char * 0x001436a8, int 1) line 30<o:p></o:p> WinMainCRTStartup() line 330 + 54 bytes<o:p></o:p> KERNEL32! 7c59893
Re:CExtControlBar that crash...or is miss used	Technical Support	Mar 19, 2005 - 10:02 AM
In the stack dump you provided there are function addresses of the Prof-UIS DLL module instead of function names. Please provide us with a more friendly stack dump. We also need more details on your application and user actions that cause this crash.
Re:Re:CExtControlBar that crash...or is miss used	Ionut Ceausu	Mar 21, 2005 - 1:43 AM
I was able to reproduce and identify the crash source. It occur when I drag an CExtControl bar onto another one and I set the desired horizontal size (SetInitDesiredSizeHorizontal(desDim.cszDesiredHorizontal)) to (0,0). I attach the source code that causes the crash. <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p> <o:p> </o:p>
Re:Re:Re:CExtControlBar that crash...or is miss used	Ionut Ceausu	Mar 21, 2005 - 1:44 AM
I mailed the source code to the support@prof-uis.com with subject See tech forum message "CExtControlBar that crash ...or is miss used" Thanks.
Re:Re:Re:Re:CExtControlBar that crash...or is miss used	Technical Support	Mar 21, 2005 - 3:41 AM
We failed to reproduce the crash in the test project you sent us. We also have a question: Why do you set the width/height of the resizable control bar to zero instead of just hiding it?
Re:Re:Re:Re:Re:CExtControlBar that crash...or is miss used	Ionut Ceausu	Mar 21, 2005 - 6:23 AM
Maybe will help somedody Yes, there is an unwanted assertion in this case, but we have not encountered any crash. Please do not hesitate to contact us if you have any questions. Best regards, Technical Support Team FOSS Software, Inc. Phones: (603) 894 6425 (603) 894 6427 Subject: RE: See tech forum message "CExtControlBar that crash ...or is miss used" Hello, Step to reproduce: 1. Close all bars that appear when open the application 2. Press "open" from the toolbar 3. A set of 3 controls bar will appear. 4. Drag one of them onto another...an access violation will occur. This is on version 2.27 Best regards, Ionut Ceausu *Prof-UIS Technical Support Team <support@prof-uis.com>* wrote:
Re:Re:Re:Re:Re:Re:CExtControlBar that crash...or is miss used	Ionut Ceausu	Mar 21, 2005 - 6:29 AM
With the same source code, on my machine I encoutered an access violation. Machine configuration: P4 2,8, Hyperthreading active, W2k SP4, Visual studio Enterprise 6.0 with sp5, platform SDK November 2001. And the crash is always reproductible. I don’t know what to say more. Best regards, Ionut Ceausu
Re:Re:Re:Re:Re:Re:Re:CExtControlBar that crash...or is miss used	Technical Support	Mar 22, 2005 - 2:15 AM
We will install exactly the same version of Platform SDK and check everything again. We do not see any other way of how to reproduce this now. Do you able to produce the crash when running release builds?
Re:Re:Re:Re:Re:Re:Re:Re:CExtControlBar that crash...or is miss used	Ionut Ceausu	Mar 24, 2005 - 5:49 AM
I have the trial version of the prof uis...so I’m not able to build a release version.
Re:Re:Re:Re:Re:Re:Re:Re:Re:CExtControlBar that crash...or is miss used	Technical Support	Mar 24, 2005 - 11:22 AM
We can provide you with a release version. Please send us an e-mail in which specify the version of Visual Studio you are using and which service pack if any is installed. You will be able to download the required dll/lib files from our ftp site.