Hi Dave, Deep breathing...it helps;-)
Tiemo was saying that your case is pretty clearly an issue of the unintended consequences of different parts of code interacting. Asking for someone to look at the code most likely won't reveal the bug because they have no context for the other interactions that are taking place in your code. I realize you must have a very complex set of interactions, but is there any way to remove some of them and then start adding them back in until you find the one that triggers the combination with alwaysBuffer to cause the crash? -- cb On 6/22/07, Dave <[EMAIL PROTECTED]> wrote:
On 22 Jun 2007, at 15:06, Tiemo Hollmann TB wrote: > I would say "looking into the source code" without having explicit > details Well you are wrong then! That's how bugs gets fixed. I have had a similar problems in the past where someone has looked at the source code and been able to find a work around for a particular problem. There can only be so many causes for a crash, in this case it obviously has to do with buffering, maybe a buffer is being freed in error or maybe, when I am running the main application, a allocation request fails and it's not checked for and so results in a crash. All the Best Dave _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
