BorlandTalk.com Borland discussion newsgroups   Archives   FAQ   Search   Memberlist   Usergroups   Register   Profile   Log in to check your private messages   Log in  QC Error 22163 - Assertion failure: "pe" in ..win32srceval          BorlandTalk.com Forum Index -> C++ Builder (Non-Technical) View previous topic :: View next topic   Author Message Charles Pope Guest Posted: Thu Mar 29, 2007 5:49 pm    Post subject: QC Error 22163 - Assertion failure: "pe" in ..\win32src\eval We seem to get a lot of this error when debugging and opening a file within our client application on a fairly random basis. I doubt there is a simple reproduceable case, but if anyone has experience of dealing with this error any comments would be gratefully received. Since it has an explicit line number, what does it relate to? Is there a good workaround, as it is becoming very frustrating for our developers. Thanks Charles Back to top Jonathan Benedicto Guest Posted: Thu Mar 29, 2007 8:04 pm    Post subject: Re: QC Error 22163 - Assertion failure: "pe" in ..\win32src\ Charles Pope wrote: Quote: We seem to get a lot of this error when debugging and opening a file within our client application on a fairly random basis. I doubt there is a simple reproduceable case, but if anyone has experience of dealing with this error any comments would be gratefully received. Since it has an explicit line number, what does it relate to? Is there a good workaround, as it is becoming very frustrating for our developers. Do you have TortoiseSVN installed? If so, try getting the latest version. Fixed this problem for me. HTH Jonathan Back to top Dennis Jones Guest Posted: Thu Mar 29, 2007 8:27 pm    Post subject: Re: QC Error 22163 - Assertion failure: "pe" in ..\win32src\ "Charles Pope" <public (AT) nospam (DOT) charlespope.com> wrote in message news:460bb4d6 (AT) newsgroups (DOT) borland.com... Quote: We seem to get a lot of this error when debugging and opening a file within our client application on a fairly random basis. I doubt there is a simple reproduceable case, but if anyone has experience of dealing with this error any comments would be gratefully received. Since it has an explicit line number, what does it relate to? Is there a good workaround, as it is becoming very frustrating for our developers. There are no fewer than 4 reports on this issue (three of which are marked as duplicates of another) and one (and only one!) of them says it is fixed. One says it's caused by TortoiseSVN, another says it's caused by a printer driver. Have you read the workarounds/comments on these to see if they help at all? Report No: 22163 Status: Closed Assertion failure: "pe" in ..\win32src\eval32.cpp at line 1692 http://qc.codegear.com/wc/qcmain.aspx?d=22163 Report No: 22378 Status: Open Assertion failure "pe" http://qc.codegear.com/wc/qcmain.aspx?d=22378 Report No: 23631 Status: Open Assertion failure: "pe" in ..\win32src\eval32.cpp at line 1692 while debugging dll http://qc.codegear.com/wc/qcmain.aspx?d=23631 Report No: 35757 Status: Open C++ DLL project causes debugger to throw assertion http://qc.codegear.com/wc/qcmain.aspx?d=35757 On a slight tangent, don't you just love the way bugs get fixed, but they never tell you what the real cause was? Most software vendors will be explicit about the cause of bugs when they are fixed by saying something like, "Fixed bug where assertion blah blah would occur if..." And of course, they didn't close all of the reports that are marked as duplicates, nor even the report to which all of the others are linked! How do we report bugs in the QC process itself? I can think of at least two problems relating to QC that are bound to cause issues like this in the future, if they haven't already. - Dennis Back to top Charles Pope Guest Posted: Thu Mar 29, 2007 9:01 pm    Post subject: Re: QC Error 22163 - Assertion failure: "pe" in ..\win32src\ Quote: Do you have TortoiseSVN installed? If so, try getting the latest version. Fixed this problem for me. Thanks. TortoiseCVS in fact, but worth a go. Charles Back to top Dennis Cote Guest Posted: Thu Mar 29, 2007 9:24 pm    Post subject: Re: QC Error 22163 - Assertion failure: "pe" in ..\win32src\ Dennis Jones wrote: Quote: How do we report bugs in the QC process itself? I can think of at least two problems relating to QC that are bound to cause issues like this in the future, if they haven't already. Dennis, You report them using QC of course. ;-) Select the Quality Central project and add them as bug reports or feature requests. I agree there are lots of rough edges in the current QC process. Dennis Cote Back to top Leo Siefert Guest Posted: Fri Mar 30, 2007 5:22 pm    Post subject: Re: QC Error 22163 - Assertion failure: "pe" in ..\win32src\ Dennis Jones wrote: Quote: There are no fewer than 4 reports on this issue (three of which are marked >as duplicates of another) and one (and only one!) of them says it is fixed. I checked in RAID and it does appear that this is fixed, so I have marked the three later reports as dups of the first one and now all consistently show fixed. Not sure what went wrong, since all were already linked to the same internal report and should have all shown the same status. Also found the information that this apparently does not happen with version 1.4 of Tortoise. (I have not tested this.) Report No: 22163 Status: Closed (Fixed) Assertion failure: "pe" in ..\win32src\eval32.cpp at line 1692 http://qc.codegear.com/wc/qcmain.aspx?d=22163 Report No: 22378 Status: Closed (Duplicate of 22163) Assertion failure "pe" http://qc.codegear.com/wc/qcmain.aspx?d=22378 Report No: 23631 Status: Closed (Duplicate of 22163) Assertion failure: "pe" in ..\win32src\eval32.cpp at line 1692 while debugging dll http://qc.codegear.com/wc/qcmain.aspx?d=23631 Report No: 35757 Status: Closed (Duplicate of 22163) C++ DLL project causes debugger to throw assertion http://qc.codegear.com/wc/qcmain.aspx?d=35757 - Leo Back to top Leo Siefert Guest Posted: Fri Mar 30, 2007 5:26 pm    Post subject: Re: QC Error 22163 - Assertion failure: "pe" in ..\win32src\ Dennis Cote wrote: Quote: I agree there are lots of rough edges in the current QC process. Yes, and I'd love to see them fixed. But I'm even more interested in seeing bugs in BCB fixed. There has been significant work done to improve the QC process and the interaction between QC and RAID (the internal system) in the past year, and I do think this is a priority for CodeGear so I expect to see more work done. - Leo Back to top Dennis Jones Guest Posted: Fri Mar 30, 2007 8:53 pm    Post subject: Re: QC Error 22163 - Assertion failure: "pe" in ..\win32src\ "Leo Siefert" <lIHATESPAMsiefert (AT) senate (DOT) michigan.gov> wrote in message news:bnvp03desmahorcjfkc7krj7ja0ij2oshd (AT) 4ax (DOT) com... Quote: Dennis Jones wrote: Not sure what went wrong, since all were already linked to the same internal report and should have all shown the same status. It is my guess that the link is one-way, and only marking the report to which others are linked causes a cascade effect. But marking one of the dependent reports does not affect the original report. Just a guess. - Dennis Back to top Charles Pope Guest Posted: Tue Apr 03, 2007 1:36 am    Post subject: Re: QC Error 22163 - Assertion failure: "pe" in ..\win32src\ Quote: I checked in RAID and it does appear that this is fixed, so I have marked the three later reports as dups of the first one and now all consistently show fixed. Not sure what went wrong, since all were already linked to the same internal report and should have all shown the same status. Is it fixed in one of the recent hot fixes for 2006? Or is it something fixed in a future version. Charles Back to top David Dean [CodeGear] Guest Posted: Tue Apr 03, 2007 2:06 am    Post subject: Re: QC Error 22163 - Assertion failure: "pe" in ..\win32src\ In article <46116844$1 (AT) newsgroups (DOT) borland.com>, Charles Pope <public (AT) nospam (DOT) charlespope.com> wrote: Quote: Is it fixed in one of the recent hot fixes for 2006? Or is it something fixed in a future version. It was fixed in Delphi 2007. -- -David Dean CodeGear C++ QA Engineer <http://blogs.codegear.com/ddean/> Back to top Charles Pope Guest Posted: Tue Apr 03, 2007 3:02 am    Post subject: Re: QC Error 22163 - Assertion failure: "pe" in ..\win32src\ Quote: Is it fixed in one of the recent hot fixes for 2006? Or is it something fixed in a future version. It was fixed in Delphi 2007. That's a shame, as it won't help those of us using C++. Charles Back to top Charles Pope Guest Posted: Tue Apr 03, 2007 3:10 am    Post subject: Re: QC Error 22163 - Assertion failure: "pe" in ..\win32src\ Quote: It was fixed in Delphi 2007. That's a shame, as it won't help those of us using C++. Just further on that. Since the cause is now known - is there a good workaround in 2006? Thanks Charles Back to top David Dean [CodeGear] Guest Posted: Tue Apr 03, 2007 3:57 am    Post subject: Re: QC Error 22163 - Assertion failure: "pe" in ..\win32src\ In article <46117e51 (AT) newsgroups (DOT) borland.com>, Charles Pope <public (AT) nospam (DOT) charlespope.com> wrote: Quote: Just further on that. Since the cause is now known - is there a good workaround in 2006? Update to the latest Tortoise SVN. -- -David Dean CodeGear C++ QA Engineer <http://blogs.codegear.com/ddean/> Back to top Charles Pope Guest Posted: Wed Apr 04, 2007 8:10 am    Post subject: Re: QC Error 22163 - Assertion failure: "pe" in ..\win32src\ Quote: Just further on that. Since the cause is now known - is there a good workaround in 2006? Update to the latest Tortoise SVN. We are using Tortoise CVS, but not SVN. We will try updating, but we have relatively recent versions and I think it does not share the same core code of SVN any more. I could be wrong of course. Charles Back to top Display posts from previous: All Posts1 Day7 Days2 Weeks1 Month3 Months6 Months1 Year Oldest FirstNewest First         BorlandTalk.com Forum Index -> C++ Builder (Non-Technical) All times are GMT Page 1 of 1   Jump to: Select a forum C++ Builder Newsgroups----------------C++ BuilderC++ Builder (ActiveX)C++ Builder (Announcements)C++ Builder (Command Line Tools)C++ Builder DatabasesC++ Builder Databases (ADO)C++ Builder Databases (Desktop)C++ Builder Databases (InterBase Express)C++ Builder Databases (Multi-Tier)C++ Builder Databases (SQL Servers)C++ Builder (Graphics)C++ Builder (IDE)C++ Builder (Internet)C++ Builder (Internet Socket)C++ Builder (Internet Web)C++ Builder (Jobs)C++ Builder (Language)C++ Builder (Language C++)C++ Builder (Compatibility with MFC)C++ Builder (Native API)C++ Builder (Non-Technical)C++ Builder (Students)C++ Builder (Third Party Tools)C++ Builder (Upgrade)C++ Builder (VCL)C++ Builder (VCL Components Usage)C++ Builder (VCL Components Development)C++ Builder (VCL Usage)C++ Builder (WinAPI)C++ Builder Installation Delphi Newsgroups----------------Delphi (General)Delphi ActiveX Controls UsageDelphi ActiveX Controls DevelopmentDelphi As400Delphi DatabasesDelphi Databases (ADO)Delphi Databases (dbExpress)Delphi Databases (Desktop)Delphi Databases (InterBase Express)Delphi Databases (Multi-Tier)Delphi Databases (SQL Servers)Delphi DeploymentDelphi GraphicsDelphi IDEDelphi InternationalizationDelphi InternetDelphi Internet Isapi-WebBrokerDelphi Internet WebSnapDelphi Internet WinsockDelphi JobsDelphi Language BASMDelphi Language ObjectPascalDelphi Model Driven Architecture (General)Delphi Model Driven Architecture (Third Party)Delphi MultimediaDelphi Native APIDelphi Non-TechnicalDelphi ObjectPascalDelphi OLE AutomationDelphi OO designDelphi OpenToolsAPIDelphi Reporting-ChartingDelphi RTLDelphi StudentsDelphi TeamSourceDelphi Thirdparty ToolsDelphi Thirdparty Tools (General)Delphi Thirdparty Tools (IntraWeb)Delphi Thirdparty Tools (RaveReports)Delphi UpgradeDelphi VCLDelphi VCL ComponentsDelphi VCL Components UsingDelphi VCL Components WritingDelphi WebServices SOAPDelphi WinAPIDelphi XMLDelphi Installationcomp.lang.pascal.delphi.components.misccomp.lang.pascal.delphi.components.usagecomp.lang.pascal.delphi.components.writingcomp.lang.pascal.delphi.databasescomp.lang.pascal.delphi.misccomp.sources.delphi JBuilder Newsgroups----------------JBuilderJBuilder AnnouncementsJBuilder Applet IssuesJBuilder As400JBuilder CompilerJBuilder CORBA/RMIJBuilder DatabasesJBuilder DB SwingJBuilder DebuggerJBuilder DeploymentJBuilder DocumentationJBuilder EnterpriseJBuilder HandheldJBuilder IDEJBuilder JavaJBuilder JavaAPIJBuilder Java LanguageJBuilder Java SwingJBuilder Java BeansJBuilder Java Beans UsageJBuilder Java Beans DevelopmentJBuilder JBCLJBuilder JDataStoreJBuilder JobsJBuilder LinuxJBuilder MacintoshJBuilder & MobileSetJBuilder MultiLingual AppsJBuilder Non-TechnicalJBuilder OpenToolsJBuilder Servlets (JSP)JBuilder StudentsJBuilder Team DevelopmentJBuilder Thirdparty ToolsJBuilder UpgradeJBuilder Installation InterBase Newsgroups----------------InterBaseInterBase Bug DiscussionInterBase GeneralInterBase IBConsoleInterBase OpenSourceInterBase ReplicationInterBase SQLInterBase ThirdpartyInterBase Installation Miscellaneous Borland Newsgroups----------------AppCenterAppServerEnteraVisiBroker  You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum Powered by phpBB © 2001, 2006 phpBB Group SEO toolkit © 2004-2006 webmedic.