|
From: Nicholas N. <n.n...@gm...> - 2009-07-12 22:45:27
|
On Mon, Jul 13, 2009 at 8:33 AM, Simon Gornall<sim...@ma...> wrote: > > 1) There's a piece of code not under my control that has a memory- > access issue > 2) Valgrind kills my program whenever there's a memory-access issue > > What I'd like valgrind to do (in this case) is run my program, report > the problem, and not kill my program if it's in the 'suppressed' file > > Is it possible to do that ? From what you say above, I got the > impression that it was just the reporting of the problem that the > suppression file affects, not whether valgrind kills my program. Correct; ie. the suppressions file won't help. > I'd > happily take valgrind just reporting the issue (and me subsequently > ignoring it) if I could get past the SIGSEGV :) 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 :( Nick |