|
From: Julian S. <js...@ac...> - 2006-07-20 17:00:36
|
I don't think it would be hard to fix this. Basically what needs to happen is V needs to note any memory segments that refer to devices and not to prod around in those areas during leak checks. That's what Jeremy's original implementation did and I guess it worked for him. The real problem is I don't have a machine with relevant card+driver on which I can implement/test a fix. Aside from that I'd be happy to give it a go. J > > IIRC, that bug was fixed in earlier versions but > > then became "unfixed" a bit > > later, unfortunately. > > > >From what I see at the mailing list, it seems like > > very few people use Valgrind together with ATI > drivers, so I'm wondering if this bug is considered > worthy of being fixed, or if it's given low priority. > The fact that both 3.1.0 and 3.2.0 have the bug make > me suspect there's no input about this from the user > base... > > In the meantime, I suppose I can use Valgrind except > for leaks, and another tool for leaks (because it > seems memory leak detection is the only memcheck > option that freezes the system). > > asiga > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |