[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::c_plus_plus

Title:	C++
Notice:	Read 1.* and use keywords (e.g. SHOW KEY/FULL KIT_CXX_VAX_VMS)
Moderator:	DECCXX::AMARTIN

Created:	Fri Nov 06 1987
Last Modified:	Thu Jun 05 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3604
Total number of notes:	18242

3408.0. "Problems trying to debug programs generated by Galaxy from Visix " by MXOC00::MJUAREZ () Wed Jan 22 1997 19:19

T.R	Title	User	Personal Name	Date	Lines
3408.1	Visix Galaxy	DECC::SULLIVAN	Jeff Sullivan	`Thu Jan 23 1997 11:21`	46
3408.2	More info coming	DECCXX::MITCHELL		`Fri Jan 24 1997 10:43`	3
	There's a restriction on using ladebug from within FUSE. I'll enter another reply with more details soon.
3408.3		MXOC00::MJUAREZ		`Sun Jan 26 1997 14:45`	7
	I'll be waiting your info. Thanks in advance
3408.4	Any news about ladebug and DECfuse ?	MXOC00::MJUAREZ		`Thu Feb 06 1997 11:31`	0
3408.5	Best idea: Use DUNIX V3.2C or later with fuse V3.1 or later	DECCXX::MITCHELL		`Fri Feb 07 1997 12:46`	36
	For starters, please read the information on ladebug and fuse in the DEC C++ release notes (/usr/lib/cmplrs/cxx/DECCXX550.release-notes). I checked with the fuse group to get some information on the latest fuse versions. Whether or not the debugger shipped with DEC C++ can be invoked from within fuse depends on the OS version and fuse version that the customer is using.. Digital UNIX V4.0 or later There shouldn't be a problem invoking the debugger from fuse with any version of fuse supported on Digital UNIX V4.0 or later. The latest fuse version in V3.1. Digital UNIX V3.2c or later There shouldn't be a problem if the customer using fuse version V3.1, which supports Digital UNIX V3.2c or later. However, if the customer is using fuse V2.1 or 2.1A, the debugger shipped with the compiler (and required by the compiler) cannot be invoked from within fuse. (See additional information in the release notes about the restriction.) Digital UNIX V3.2, V3.2a or V3.2b Fuse V2.1 and 2.1A are supported on these versions; later versions of fuse are not. If the customer is in this situation, the debugger shipped with the compiler (and required by the compiler) cannot be invoked from within fuse. (See additional information in the release notes about the restriction.) If the customer is running Digital UNIX V3.2c or later, the best solution is to upgrade to fuse V3.1. If there is still a problem, it's a bug. Please report it. If the customer is running Digital UNIX V3.2, V3.2a or V3.2b, the restriction applies, and the customer will have to invoke the debugger from the command line rather than from within fuse.