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

Andre Mueninghoff andre_mueninghoff at fastmail.fm
Tue Apr 10 15:38:23 PDT 2007



On Tue, 10 Apr 2007 14:26:43 -0700, "D John Anderson"
<john at osafoundation.org> said>
> 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.

Ah, sounds like that in the debug build at least I will get a heads-up
that there could be trouble ahead. For this one, I'm not sure what
triggered it...possibly when I attempted to right-click on the Dashboard
collection in the sidebar and missed at first with the pointer. 

Also, I have also seen the event status field in the detail view go
blank/white (as in no visible data and no dropdown control) a couple of
times accompanied by an assert failure. I hadn't repoprted it, because I
was trying to figure out a reproducible pattern. Thought I'd mention it
here. I'll send the traceback in a bug report if it happens again.

Thanks, Andre


More information about the chandler-users mailing list