Very Computer

>    Where can locate a graphics oriented de* that will run
>under fvwm? I remember one from work called "ups" or "upm" or
>something to that effect. It was pretty good.

> The files are currently available at:

>   ftp.x.org:/contrib/devel_tools/ups-2.45.2-linux-rga.README
>   ftp.x.org:/contrib/devel_tools/ups-2.45.2-linux-rga.diff.gz

> and likely soon at:

>   sunsite.unc.edu:/pub/Linux/devel/de*s
> and perhaps
>   sunsite.unc.edu:/pub/X11/contrib/devel_tools

> This patch file combines the standard UPS linux port from Rick Sladkey

> optimized code, as well as my enhancements and bug fixes that I
> original develioped for SunOS. These files replace my older patch
> file that had to be applied after the linux patch. I have combined
> the patch files, fixed the rejects that were previously generated, and
> resolved some bugs in reading g++ symbol tables. The major caveat
> is that I don't have access to a Linux machine, and only limited testing
> has been done on Linux by others.

> The main features of my patch are:
> . support for reading g++ and cfront C++ symbol tables (though not ELF format)
> . demangling for C++ code
> . clicking on symbols in the source will search the `this' pointer
>   and unions
> . breakpoints automaticaly duplicated on overloaded/multiple linked methods.
> . special format option for Rogue Wave strings.
> . signal options to handle ODI's Object Store
> . attach and detach buttons
> . X text selections anywhere in the tool
> . fixes for files processed by Purify, Purelink, Insure.
> . individual and global activation of breakpoints
> . source search paths can be added interactively
> . source files can be reloaded or rematched in the source search path list
> . initialization file for setting paths, libraries to load or not load,
>   breakpoints, and tool initialization such as signals.
> . ability to launch an editor at the current source line
> . new and easier editing keys
> . more explicit messages about problems with files and libraries
> . accelerators for the most commonly used actions in the data window
> . buttons for moving up and down the stack trace
> . a button for repeatedly executing breakpoint code
> . fixes to read g++ symbol tables

> ... plus many more things as detailed in the README file.

> Comments and suggestions welcome.

> Rod Armstrong