On Mon, 2009-07-13 at 08:45 +1000, Nicholas Nethercote wrote: > > http://www.valgrind.org/docs/manual/faq.html#faq.crashes is relevant > here. It looks like you are in an unlucky situation. Probably the > best thing you can do is report any Valgrind errors that occur before > the crash to nVidia, and hope that the next version of the driver > works better :(
Given this is a device driver and GPU off-load code it could well not be to do with errors in the driver but possibly that the driver has mapped some pages into userspace that Valgrind doesn't know about? As I recall OpenGL didn't work on Linux for a couple of years for just this reason. Are there any "unrecognised syscall" errors before the crash? Ultimately I suppose the cause doesn't make any difference, all you can do is try and find a way of running the code using different library's, the use of a software renderer sounds like a promising solution. Ashley, -- Ashley Pittman, Bath, UK. Padb - A parallel job inspection tool for cluster computing http://padb.pittman.org.uk ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
