On Mon, 2004-04-19 at 12:01, Neal Norwitz wrote: > On Mon, Apr 19, 2004 at 11:47:08AM -0400, Nick Bastin wrote: > > > > On Apr 19, 2004, at 11:42 AM, Neal Norwitz wrote: > > > > >On Mon, Apr 19, 2004 at 11:36:51AM -0400, Barry Warsaw wrote: > > >> > > >>puremodule.c could probably be deprecated. Does anybody use Purify > > >>anymore -- and if so, have you ever used puremodule? Does it still > > >>compile? Are the APIs it uses still up-to-date? > > > > > >Although I did use Purify on python years ago, I never use it now. > > >Though, I never used the puremodule. IMO, Purify is not useful > > >compared to valgrind. +1 on deprecating puremodule.c. > > > > I think it's useful to point out that Purify runs on a lot more > > platforms than valgrind does, so we should probably keep puremodule > > around, and update it if necessary. > > Valgrind runs on x86 and PPC (still experimental). > IIRC, Purify "runs" on Solaris, HPUX, Windows (x86), and SGI? > (I tried to verify but the IBM site isn't responding.) > IMO that's not a lot. I was able to get to this page: http://www-306.ibm.com/software/awdtools/purifyplus/unix/ and it looks like the suite of tools runs on "Linux" now too. > Where Purify "running" is relative to any particular patch you have > installed on the system and if you can download a beta. I stopped using > Purify because Rational was so awful to deal with. -Barry
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4