On Jul 12, 2009, at 3:14 PM, tom fogal wrote: > Hi Simon, > > let's keep discussions on-list. Mostly since I'm no valgrind expert, > and if I make incorrect statements I'd like one to jump in with a clue > bat :)
Yeah, I hit 'reply' rather than 'reply-all'. I actually re-posted it to "users" afterwards :) > > > Simon Gornall <[email protected]> writes: >> >> On Jul 12, 2009, at 2:02 PM, tom fogal wrote: >> >>> Simon Gornall <[email protected]> writes: >>>> I'm trying to run my application under valgrind, and it's failing >>>> when I initialise the OpenGL context... >>> [snip] >>>> I started off with more-specific suppressions, but even with the >>>> above, the application is aborted every time I run. >>> >>> This sentence implies you are slightly confused about the >>> semantics of a suppression file. These files are merely to >>> suppress *reporting* of errors; the existance or not of any given >>> suppression should not change the behavior of a program. It will >>> certainly change what valgrind prints out, but not what's going on >>> under the hood. >> >> Ah - yes, I was hoping it was more along the lines of "yes, I know >> there's an issue there, just ignore it for now". I take it there's no >> way of doing that, then ? > > Sorry, "that" reads ambiguously to me. You mean no way of modifying > the behavior of a program using valgrind? No, not beyond the normal > valgrind instrumentation. A suppression is your way of saying exactly > what you've put in quotes, if I was unclear earlier. Right. The problem (for me at least) is that 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. I'd happily take valgrind just reporting the issue (and me subsequently ignoring it) if I could get past the SIGSEGV :) > > >>> Since you're using nvidia's driver, I'd ask you to re-run using the >>> command line option `--smc-check=all'. > [snip] >> Yep, it fails in the same way. > > Doh, sorry that wasn't any help :( > >>> If that fails, I suggest linking your program against Mesa [. . .] >> >> Thanks, I'll see if that helps - the application uses CoreImage (and >> therefore a lot of GPU shader code) quite heavily though, so I'm not >> sure if Mesa is up to it (I haven't used it in a decade or so, so I >> might be unfairly maligning Mesa :) > > I do GPU-based raycasted volume rendering through Mesa quite > regularly. > It works. The swrast Mesa backend supports OpenGL 2.1. It's about an > order of magnitude slower than my nvidia card. > > It's also about 2 order of magnitudes faster than Apple's software > fallback. Cool - I'll give it a go then :) ATB, Simon ------------------------------------------------------------------------------ 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
