Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ fuse(1) — FUSE 4.2

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

atom(1)

emacs(1)

fusescript(1)

fusebuild(1)

fuseclass(1)

fusecg(1)

fusexref(1)

fusecm(1)

fusecompare(1)

fusemerge(1)

fusedebug(1)

fuseedit(1)

fusewinedit(1)

fuseheap(1)

fuseman(1)

fusewinman(1)

fuseprof(1)

fuseport(1)

fusepv(1)

fusesearch(1)

fusevc(1)

gprof(1)

hiprof(5)

ladebug(1)

make(1u)

pixie(5)

prof(1)

third(5)

fuse(1)  —  Commands

Name

fuse − OSF/Motif window-based environment for software development, analysis, and maintenance. 

Syntax

fuse [ option ... ]

Description

DEC FUSE is a software development, analysis, and maintenance environment for UNIX programmers.  FUSE offers a set of tools with a Motif user interface.  These tools include editors, program builder, source code managers, debugger, cross-referencer, call graph browser, file comparison tool, man page hypertext viewer, search tool, performance profiler, heap analyzer, program visualizer, and optional C++ class browser. 

The fuse command starts a FUSE session. FUSE displays the Control Panel, from which you can start all other FUSE tools.  You can also start individual tools directly from the command line or using the Common Desktop Environment (CDE) (see individual manpages and the FUSE online help for more information).

The Control Panel lists the currently open projects and tools running within those projects.  When you choose a tool from the Tools menu, FUSE starts the tool in the current project and lists it in the Control Panel display area. 

FUSE provides the following online help:

•FUSE Overview −  If you are a new FUSE user, on the Control Panel’s Training menu, choose Getting Started with FUSE. 

•FUSE Tutorials − For step-by-step tutorials on using FUSE tools, choose FUSE Tutorials from any tool’s Help menu (or from the Training menu on the Control Panel). 

•Tool overview − From a tool’s Help menu, choose On <tool> (where <tool> is the name of the tool you are currently using) to get information about the tool, using its main window, and using its menus. 

•Dialog box − Click on the Help button in a dialog box to get information about using that dialog box.  Information for error dialog boxes describes how the error may have occurred and how to recover from the error. 

•Screen objects − Choose the On Context item from a tool’s Help menu to display item-specific information.  When you choose On Context, the pointer changes to a question mark. You can move the question mark to a screen object such as a field or menu in a main window and click MB1 to display information about it. 

•Quick-reference information -- When you pull down a menu and drag the pointer over the items on the menu, a brief description of the item beneath the pointer appears in the information area at the bottom of the tool’s window. 

Options

−D Starts FUSE in debugging mode, and optionally, with local fuseschema.msl and tools.rc files.

−display local-system:monitor
Specifies the local system on which to display the Control Panel.  For example: % fuse -display locsys:0.0

−nott
Do not start the ToolTalk server.

−nostart
Causes tools that were invoked and saved as part of a project to not be started as they normally would when FUSE is started from the command line.

−proj project-file-name
Starts FUSE with the specified project file.  A project file allows you to reestablish your work context. When you start FUSE using this option, the project-wide data is restored for use by all tools in the project.  FUSE automatically saves project data for the current project when you exit FUSE.

−rc path
Specifies the absolute pathname of the resource file, tools.rc, produced by the TIL compiler.

−schema path
Specifies the absolute pathname of the schema file, fuseschema.msl, produced by the TIL compiler.

−tt Always start the ToolTalk server.  By default, the ToolTalk server will be started on systems where the command /usr/dt/bin/ttsession exists and is executable when this option and the following one are not present. The ToolTalk server will not be started by default when /usr/dt/bin/ttsession does not exist or is not executable. 

−xref target-dir
Creates a static analysis database for the specified target directory without starting a FUSE session.  You must already have generated static analysis data files.  See the DEC FUSE Handbook or the online Help for more information on generating static analysis data files. 

FUSE accepts all of the standard X Toolkit command line options (see X(1)). 

For more information on creating the fuseschema.msl and tools.rc files, refer to the DEC FUSE EnCASE Manual and the til(1) reference page. 

Restrictions

FUSE supports distributed display but not distributed access.  Tools must run on the same system, and the directory paths that you specify cannot include node names. 

You can run multiple instances of the same tool in a project, with the exception of the Builder.  You can run only one instance of the Builder in a project. 

The Database Manager also assumes that global names are global to all the programs in the directory tree being searched.  This assumption can cause unexpected results.  For example, if unrelated programs include variables or functions with the same name, the Database Manager may see a cross-reference or call relationship where none really exists. 

Supplemental Copyright Information

Copyright (c) 1980 Regents of the University of California. 
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1.  Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 

2.  Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 

3.  All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the University of California, Berkeley and its contributors. 

4.  Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. 

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 

See Also

atom(1), emacs(1), fusescript(1), fusebuild(1), fuseclass(1), fusecg(1), fusexref(1), fusecm(1), fusecompare(1), fusemerge(1), fusedebug(1), fuseedit(1), fusewinedit(1), fuseheap(1), fuseman(1), fusewinman(1), fuseprof(1), fuseport(1), fusepv(1), fusesearch(1), fusevc(1), gprof(1), hiprof(5), ladebug(1), make(1u),  pixie(5), prof(1), third(5)

DEC FUSE Handbook

DEC FUSE EnCASE Manual (online on the documentation CD)

Ladebug Debugger Manual: Window and Command-Line Interface

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026