[chandler-users] Differences between End-User and Debug Builds regarding C++ assertion "wxAssertFailure" type issues

[D John Anderson]

On Apr 10, 2007, at 1:11 PM, Andre Mueninghoff wrote:

> Hi, In a thread about the behavior of the search tool in Chandler,  
> Dan had mentioned that one would not see that assert type failure  
> in the End-User build that I was seeing in the Debug build. Q. Is  
> this a general guideline that dogfooders might follow?

This is a real bug that needs to be fixed. The only reason the  
release version doesn't report it is because it's missing the testing  
code.

>
> It seems to me that when I see an AssertFailure type message in the  
> console (example pasted below), Chandler will fail to restart with  
> the same build, same everything else, (including a clean result  
> from Check and Repair prior to closing the instance in which the  
> AssertFailure error was generated). Instead I get the Windows C++  
> Abort/Retry/Ignore dialog box, after which the only recourse to  
> date seems to be to start over with a new empty repository. Given  
> the dev team's focus on performance for the near term, I am  
> considering using End-User builds instead of the Debug builds for  
> awhile. Thoughts?

When you get this bug in the debug build, does running release after  
that work?, or do you still get failures?

As a general rule of thumb, running debug builds is more useful to us  
because it reports errors that are ignored in the release builds --  
and there is usually a good reason why those errors are a problem, so  
running in the release version doesn't mean you're any safer.

John

P.S. I'll file a bug for me to fix this.

>
> Thanks much,
> Andre
>
> <DBRepository>: 2007-04-10 15:51:58.955000, completed checkpoint
> Traceback (most recent call last):
>   File "C:\Program Files\Chandler0.7alpha5\application 
> \Application.py", line 833
> , in OnContextMenu
>     blockItem.widget.displayContextMenu(event)
>   File "C:\Program Files\Chandler0.7alpha5\parcels\osaf\framework 
> \blocks\Table.p
> y", line 183, in displayContextMenu
>     theApp.Yield()
>   File "C:\Program Files\Chandler0.7alpha5\debug\bin\lib\site- 
> packages\wx\_core.
> py", line 7129, in Yield
>     return _core_.PyApp_Yield(*args, **kwargs)
> wx._core.PyAssertionError: C++ assertion "wxAssertFailure" failed  
> at \cygwin\hom
> e\builder\tinderbuild\external\wx\wxPython-r163\src\msw\app.cpp 
> (680) in wxApp::Y
> ield(): wxYield called recursively
> <DBRepositoryView: MainThread (119)> committed 384 items (212  
> kbytes) in 0:00:03
> .453000, 111 items/s (61 kbytes/s)
> closed db in 0:00:04.687000
> [5411562 refs]
>
> _______________________________________________
> chandler-users mailing list
> chandler-users at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/chandler-users