Thanks for the input! I have run it through valgrind before and didn't pick up anything weird, but I think I will have to investigate this route more thoroughly (I admit to doing some nasty raw pointer work with this guy, but the fact that it ran so smoothly on Linux made me think I had nailed all the issues).
Any amazing settings/valgrind options you prefer when valgrinding with QtCreator (or command line)? PS Bo...I agree with you re system bugs, I am pretty sure the issue is on my side, but now to find it! :D On 21 November 2013 10:19, Koehne Kai <kai.koe...@digia.com> wrote: > > > -----Original Message----- > > From: interest-bounces+kai.koehne=digia....@qt-project.org > > [mailto:interest-bounces+kai.koehne=digia....@qt-project.org] On Behalf > Of > > Bo Thorsen > > Sent: Thursday, November 21, 2013 7:43 AM > > To: interest@qt-project.org > > Subject: Re: [Interest] Windows segfault, but not on Linux > > > > Hi William, > > > > Sounds like you have quite a nightmare of a bug there. > > > > I don't have a solution for you, but I can tell you my starting points > for trying to > > figure this one out. > > > > First is *always* this one: Have you run your application in valgrind? > > I'd start with that too, and here's why: Such 'weird' errors in seemingly > unrelated code paths are often enough a sign of a memory corruption going > on ... i.e. you're writing to invalid pointers etc somewhere else in your > code. > > Regards > > Kai > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest >
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
