Conference turris::decladebug

The debugger support for C++ V5.6 didn't go in until 4.0-35.  You should
upgrade your debugger and try again.  If you still have problems, then report
back here.

-Chris

If you are using the v5.6 C++ compiler, you will want to use the
latest-greatest ladebug (currently 4.0-37).  

Support for this compiler is still a work in progress.  4.0-38, due 
shortly, will include additional support and addresses all the major
issues reported to date.

-Steve

Hello,

	The problem still occurs using Ladebug 4.0-37.


	The Rogue Wave Tools++.h release : V7.0.3

	If it can help you, I generate my executable using the
	following compilation commands:

	I'm trying to debug an executable linked with my own shared-library 
	(with is linked with Rogue Wave too) and with the Rogue Wave Library.

	Command line used to build an object of my own shared-library:
	---------------------------------------------------------------

	cxx -c -pthread -nopt   -w0 -G 0  -I. -I/usr/include/cxx
	 -I/usr/include/cxx/sys -I/usr/include -I/usr/include/dce 		
	-I/usr/mcc/mmtoolkit/include -I/usr/mcc/mmtoolkit/dev 	
	-I/usr/kits/TNM310/files/dev   -g  -DRW_MULTI_THREAD -D_REENTRANT 
	-DRW_NO_EXCEPTIONS -O0 -trapuv -DMCC_DISTRIB   -DTEMIP_PORTABLE 
	 tfc_wp_trace.cxx


	Command line used to link my shared-library:
	---------------------------------------------------------------

	cxx -shared  -O0 -pthread  -o libtfc_wp.so ...... -ltemip -ltfc_sp
	 -lrwtool_mt -lmcc_exec -lmcc_parpml -lmcc_sys  -ltns  -llmf -lbsd -lm


	Command line to build a Rogue Wave object file:
	---------------------------------------------------------------

	cxx  -I.. -D_RWBUILDSHARED -DRW_MULTI_THREAD -D_REENTRANT
	 -DRW_NO_EXCEPTIONS   -Wl,-call_shared -pthread -c idlistit.cpp


	Command line to build the Rogue Wave shared library:
	---------------------------------------------------------------

	cxx -pthread -shared -expect_unresolved "*" -o librwtool_mt.so
	 ....<object files>


	Command line to build my executable:
	---------------------------------------------------------------

	cxx -call_shared  -O0 -pthread  -o tfc_cache_dict_builder
	 tfc_cache_dict_builder.o -ltfc_sp  -ltfc_wp -lrwtool_mt  -lmcc_exec
	 -lmcc_parpml -lmcc_sys  -ltns  -llmf  -lbsd -lm



	Thanks for your help


		Christophe Gervais

From the Ladebug release notes:

There is a problem with using any version of ladebug (or dbx) on 
certain systems that are running Digital UNIX 4.0B. The problem is 
that some systems will hang or crash when the debugger is used. 

The machines affected are the newer machines, such as the AlphaStation 
500 and 600 series machines. This is not a problem for other machines 
such as DEC 3000s and DEC 4000s. 

A kernel patch is required to fix this problem. From the 4.0B patch 
kit, install the following patch: 

      NEW PatchID: 91.00 
      PATCH ID: OSF410-053     SUBSET(s): OSFBIN410

When using setld to install the 4.0B patch kit, look for the new PatchID 
in the subset menu display to select the correct patch. The patch 
description is: "Patch: Kernal Debugger Corrections". 

The patch saves the whole system from crashing, not just Ladebug, so
I don't think it will make a difference here.

/Bevin

Hello,

	Thank for your help.

	The V4.0B Patch 0091.00 - Kernel Debugger Corrections
	is already installed on my workstation (ALPHAstation 255).

	I reproduced the problem on a simple executable
	which displays the content of a Rogue Wave String.

	If you can have a look on it.	
	
	This simple program is available on unitel.vbo.dec.com
	file location : /pub/temp/test_ladebug_rw.tar

	The tar file contains the executable and the Rogue Wave shared
	library.

	To crash the debugger just try to run the program using ladebug.

	Thanks,


		Christophe	

I tried to reproduce the problem on 4.0B system using your test program, but
everything seems to work fine.

Can you give us 

1. the version of the CXX shared library that you are using ??
2. exact commands that you typed to run your program.


Also, I noticed that you use -trapuv on the compilation command. In the past,
we have had problems with the usage of that switch and the version of CXX shared
library. Was your test program also compiled wiht -trapuv switch ??

Would you try removing that switch from your compilation command and see
if it makes a difference.

thanks
shamim
 

Bonjour,

I tried to reproduce the problem too on a DEC 3000 700. Everything work
fine too.

I perhaps comes from a hardware problem, but where ?

Concerning the version of the CXX shared, I use those installed 
by the cxx kit V560 T06.

Subsets installed by the CXX kit V560 T06:

CXXBASE560           installed  DEC C++ (cxx) for Digital UNIX
CXXHTML560           installed  DEC C++ HTML documentation
CXXMAN560            installed  DEC C++ and class library manual pages
CXXV4HDR560          installed  DEC C++ header files for Digital UNIX V4.0 or la
ter

LDBBASE437           installed  Ladebug Debugger Version 4.0-37
LDBGUI437            installed  Ladebug Debugger Window Interface


I tried with other cxx and ladebug versions.
For CXX I tried versions V540 V550
For Ladebug I tried versions V426  V430  V437.
With all of these versions, the worksation crashes.
I tried to run dxladebug, The workstation crashes before I use it.
The GUI is displayed and it crashes.


I you want I can give you an access on my workstation.


thanks,


	Christophe.
 

Hello,

        In fact the problem comes from the pthread library.
        Indeed when debugging a simple program, just linked
        with the -pthread option, the debbuger crashes the station.

        Here the C++ example:
        ---------------------

        #include <iostream.h>

        main()
        {
                cout << "Hello" << endl;
        }

        The makefile:
        --------------

        test_ladebug_rw: test_ladebug_rw.o
                cxx -pthread -o test_ladebug_rw test_ladebug_rw.o


        test_ladebug_rw.o: test_ladebug_rw.cxx
                cxx -call_shared -w0 -G 0 -g -O0 -trapuv -c test_ladebu
g_rw.cxx

	The crash occures when executing the "run" command on ladebug.

	Subsets installed by the CXX kit V560 T06:

CXXBASE560           installed  DEC C++ (cxx) for Digital UNIX
CXXHTML560           installed  DEC C++ HTML documentation
CXXMAN560            installed  DEC C++ and class library manual pages
CXXV4HDR560          installed  DEC C++ header files for Digital UNIX V4.0 or la
ter

LDBBASE437           installed  Ladebug Debugger Version 4.0-37
LDBGUI437            installed  Ladebug Debugger Window Interface




	Regards,

		Christophe
	Workstation : ALPHAstation 255/300 

>> In fact the problem comes from the pthread library.

So, which version of pthread library are using ?? Are you using special
patched version ??

And the problem only happens on particular hardware/system right ??

shamim

Indeed, the problem only happens on a Alphastation 255.

Concerning the version of the pthread library an odump of 
my executable give the following result:

        Name             Time-Stamp        CheckSum   Flags Version
test_ladebug_rw:
        libcxx.so    Nov 16 02:53:54 1996 0x966808b6     0 V4.0.1
        libpthread.so Mar 29 11:11:36 1997 0x50163f37     0 osf.1
        libmach.so   Nov 16 02:57:04 1996 0x97ad5768     0 osf.1
        libexc.so    Mar 29 06:47:56 1997 0x3184247e     0 osf.1
        libc.so      Mar 29 06:47:31 1997 0xe1df5327     0 osf.1


Christophe

Hello,
	We received some Alphastations 255/300 (which have been 
delivered with a graphical interface supported only from DUnix 4.0).
	I reproduced the Ladebug crash on these stations. 
	So we can deduce that the problem is not specific to my
	configuration.
	It's a major issue for us, so we need a solution.

 	Summury of the configuration:

	Alphastation 255/300
	OS : D-UNIX V4.0B 564
	Ladebug 4.0-37.
	CXX 5.6 T06
	Installed patch : V4.0B Patch 0091.00 - Kernel Debugger Corrections
	
	Subsets installed by the CXX kit V560 T06:

	CXXBASE560           installed  DEC C++ (cxx) for Digital UNIX
	CXXHTML560           installed  DEC C++ HTML documentation
	CXXMAN560            installed  DEC C++ and class library manual pages
	CXXV4HDR560          installed  DEC C++ header files for Digital UNIX
V4.0 or later
	LDBBASE437           installed  Ladebug Debugger Version 4.0-37
	LDBGUI437            installed  Ladebug Debugger Window Interface


	Simple reproducer:
	******************

	 Here the C++ example:
        ---------------------

        #include <iostream.h>

        main()
        {
                cout << "Hello" << endl;
        }

        The makefile:
        --------------

        test_ladebug_rw: test_ladebug_rw.o
                cxx -pthread -o test_ladebug_rw test_ladebug_rw.o


	Releases of the Shared Libraries:
	---------------------------------

  	Name             Time-Stamp        CheckSum   Flags Version
test_ladebug_rw:
        libcxx.so    Nov 16 02:53:54 1996 0x966808b6     0 V4.0.1
        libpthread.so Mar 29 11:11:36 1997 0x50163f37     0 osf.1
        libmach.so   Nov 16 02:57:04 1996 0x97ad5768     0 osf.1
        libexc.so    Mar 29 06:47:56 1997 0x3184247e     0 osf.1
        libc.so      Mar 29 06:47:31 1997 0xe1df5327     0 osf.1
	

	To reproduce the crash under Ladebug just type "r" after program
	loading.


	Best regards,


		Christophe Gervais.
		

	

	Hello,

	I entered a QAR Show-Stopper in OSF_QAR database. QAR number 53243.


	Best regards,

		Christophe.

Please pick up the BL38 kit and try that - it is possible that you are
will benefit from

        o  The debugger failed to freeze outstanding DECthreads threads in
           certain situations on SMP machines.  This problem has been fixed.
           (IPMT HPAQ416AG, LB 2203)

although it is not clear that the SMP problem also affects this hardware.

I have been reading through the information, trying to understand what is
really happening.

Here is what you have told us so far...

958.8 "the workstation crashes"
      "I tried to run dxladebug, The workstation crashes before I use it"

        [I don't understand this second remark - you mean it crashes before
         you run the gui?, the gui appears?, before you can click anything?
        ]

958.9 "the debugger crashes the station"

958.12 "I reproduced the Ladebug crash on these stations"


I think from all this, that 
	LADEBUG IS NOT CRASHING, 
but 	YOUR SYSTEM CRASHES WHEN YOU USE LADEBUG, PTHREADS, ETC.


This sounds like an O/S problem, not a ladebug problem.
I have passed it on to the kernal group.

/Bevin