[ Contact Info | Site Index ]

Frequent Questions

What does the release cost?
What is a commercial use?
What can I do if it doesn't work?
What if I find a bug?
What kind of warranty is provided?

Techinal Issues

Why can't Paradyn find libelf on my non-RedHat linux system?
Why do I get the error 'Static executable: unhandled' on linux?
Why do I get dataManager.thread.h: No such file or directory errors when building Paradyn?
Why do I get a cannot compute sizeof (char) error when building Paradyn?
Why do I get an invalid conversion from 'const char***' to 'char***' error when Paradyn tries to build uimpd.tcl.C?

What does the release cost?

For research uses, there is no charge. We define "research use" to mean you may freely use it inside your organization for whatever purposes you see fit. Our source code release is also freely available for research uses.

You may not re-distribute Paradyn in any form (including derivatives), electronic or otherwise, to any other organization or entity without our permission.

Full details of allowable uses of Paradyn are described in the LICENSE file contained in the "paradyn" and "paradyn/src" directories.

What is a commercial use?

We define "commericial use" of Paradyn to be one in which you re-distribute Paradyn in binary or source code form. Such an arrangement requires a signed license agreeement. Please contact us for the details.

What can I do if it doesn't work?

If you have any problems with installing or running Paradyn, feel free to contact us at paradyn@cs.wisc.edu. If you have problems running dyninstAPI contact us at bugs@dyninst.org. We will try to respond promptly.

We also appreciate feedback from you on ease of installation and use, and have provided an on-line experience report form for this purpose.

What if I find a bug?

Your report of bugs will help to improve future releases. Please report paradyn bugs to paradyn@cs.wisc.edu and dyninst bugs to bugs@dyninstorg. We will work on fixes or try to provide you with a "workaround". You will typically get a response in no more than 1-2 working days.

What kind of warranty is provided?

We provide the Paradyn Parallel Performance Tools (below described as "Paradyn") on an "as is" basis, and do not warrant its validity or performance. We reserve the right to update, modify, or discontinue this software at any time. We shall have no obligation to supply such updates or modifications or any other form of support to you. All warranties, including without limitation, any warranty of merchantability or fitness for a particular purpose, are hereby excluded.

By your use of Paradyn, you understand and agree that we (or any other person or entity with proprietary rights in Paradyn) are under no obligation to provide either maintenance services, update services, notices of latent defects, or correction of defects for Paradyn.

Even if advised of the possibility of such damages, under no circumstances shall we (or any other person or entity with proprietary rights in the software licensed hereunder) be liable to you or any third party for direct, indirect, or consequential damages of any character regardless of type of action, including, without limitation, loss of profits, loss of use, loss of good will, or computer failure or malfunction. You agree to indemnify us (and any other person or entity with proprietary rights in the software licensed hereunder) for any and all liability it may incur to third parties resulting from your use of Paradyn.

Why can't Paradyn find libelf on my non-RedHat linux system?
- OR -
Why do I get the error 'Static executable: unhandled' on linux?

There are two implementations of libelf available for Linux. One is libelf.so.0, which is maintained by Michael Riepe and distributed with many non-RedHat linux distributions. The other is libelf.so.1, which is maintained by Ulrich Drepper and RedHat. It is usually distributed as part of the elfutils package and can be found on most RedHat Linux systems.

These two implementations are source compatable, so Paradyn can be built and run with either one. However, they are not binary compatible, so Paradyn cannot be built against one implementation and then run with the other.

The prebuilt Paradyn binaries for Linux/x86 are linked against libelf.so.1. Attempting to run one of these binaries on a system with only libelf.so.0 installed will result in a error stating that libelf.so.1 could not be found. Attempting to circumvent this problem by symbolically linking libelf.so.1 to libelf.so.0 will cause Paradyn to fail with an assertion and print the message 'Static executable: unhandled.' We recommend installing libelf.so.1 or rebuilding Paradyn from the source code.

Why do I get dataManager.thread.h: No such file or directory errors when building Paradyn?

The dataManager.thread.* files are generated by a Paradyn utility called igen. If igen fails to build or install correctly the Paradyn build will fail with the above errors. The most common cause of igen failing to build is from not running 'make ready' before running 'make install'.

Why do I get a cannot compute sizeof (char) error when building Paradyn?

This odd error message comes from Paradyn being unable to find the flex library. Edit the make.config file and set the FLEX_LIB variable to point to the directory containing libfl.a.

Why do I get an invalid conversion from 'const char***' to 'char***' error when Paradyn tries to build uimpd.tcl.C?

Paradyn works with Tcl/Tk 8.4 or 8.3, however this must be setup correctly in make.config.local before Paradyn is built. Edit make.config.local and set USE_TCL83 to true.

 

Paradyn

Release 5.0.1 Features/Bugs
Release 5.0.1 Software
Release History

Dyninst

Release 5.0.1 Features/Bugs
Release 5.0.1 Software
Release History

Kerninst

Release 2.1.2 Features
Release 2.1.2 Software

MRNet

Release 1.1 Features
Release 1.1 Software

Frequently Asked Questions
Documentation

[ Contact Info | Site Index ]