RE: Debugging Performer apps

New Message Reply Date view Thread view Subject view Author view

Øyvind Roa (oyvind.roa++at++ks-t.no)
Wed, 1 Sep 1999 12:27:59 +0200


> >> From: Javier Taibo <jtaibo++at++udc.es>
> >> Date: Mon, 30 Aug 1999 11:37:17 +0200
> >> Subject: Debugging Performer apps
>
> >> Hi Performers,
>
> >> Has anyone used the Purify software with Performer applications?
> Does
> >> it work fine with
> >> IRIX 6.5, Performer multiprocessing, shared memory management, etc...?
>
> We use a combination of Purify and a nice little library called libdmalloc
> (part of the SGI Developer Toolbox) to trace memory problems.
> Unfortunately Purify does not directly deal with Performer
> multiprocessing,
> and shared memory management, but the libdmalloc distribution give you
> some hints on how to combine i with libdmalloc to achieve it. Together
> they give you a nice memory tracing environment.
>
> >> Do you know any other product for analysing software and looking for
> >> reads/writes out of
> >> place, memory corruption, memory leakage, etc... Is there any SGI
> tool
> >> for such kind of things?
> >> CaseVision software?
>
> >> We reached a point where our program is failing in the most
> surprising
> >> ways and places.
> >> It seems to me a clear case of memory corruption, but we can't find
> the
> >> source of the problem
> >> because the complexity and size of the code.
>
> >> Any help will be very appreciated. Thanks.
>
> >> --
> >> Javier Taibo
> >> videaLAB - E.T.S.I.C.C.P. http://videalab.udc.es
> >> Universidade da Coru=F1a e-mail: jtaibo++at++udc.es
>
> --------------------------------------------------
> Oyvind Roa
> Senior Software Engineer
>
> Kongsberg Defence & Aerospace
> P.O Box 1003
> NO-3600 Kongsberg
> NORWAY
>
> E-mail : oyvind.roa++at++kongsberg.com
> --------------------------------------------------

**********************************************************************
This footnote confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
**********************************************************************


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Wed Sep 01 1999 - 03:28:12 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.