Conference turris::decladebug

854.0. "Reference parameters don't print." by DECCXX::COLEEN () Wed Feb 26 1997 16:30

While debugging my version of the DEC C++ V6.0 compiler, I
can't seem to print out reference parameters.  If I go up a
level, I can see the parameter, though.  Also the fields off
of the look like 64 bit addresses, wehn they were compiled with
-xtaso_short.

Sample session below.  A tar file of the entire problem can be found
on cosf in ~coleen/ladebug1/exx.tar

Thanks,
Coleen

216% ladebug $CEXE/exx
Welcome to the Ladebug Debugger Version 4.0-25
------------------
object file name: /usr/lusers/coleen/decc/exxalphaosf/bl36/exe/exx
Reading symbolic information ...stop in done
(ladebug) stop in walk_try_block_statement
[#1: stop in void walk_try_block_statement(a_statement&) ]
(ladebug) go
go
 ^
Unable to parse input as legal command or C expression.
(ladebug) run -gem_be vsimple.cxx
[1] stopped at [void walk_try_block_statement(a_statement&):291 0x6ff9fda0]
    291     a_try_supplement_ptr try_block = stmt.variant.try_block;
(ladebug) ex stmt
<bad reference>
(ladebug) W
    281 //
    282 {
    283     current_function_edata->current_try_block = parent;
    284 }
    285
>   291     a_try_supplement_ptr try_block = stmt.variant.try_block;
    292     a_label_ptr end_label = DEC_SUPP(*try_block).end_label;
    293
    294     // Create a new middle end try block and link it as the current tr
block.
    295     an_me_try_block *tb = new an_me_try_block;
    296
    297     // Assign the try block number to the current_try_block_decl
    298     update_current_try_block(current_function_edata->current_try_block
ndex());
    299
    300     // Create the VBRANCH sequence
(ladebug) n
stopped at [void walk_try_block_statement(a_statement&):292 0x6ff9fdac]
    292     a_label_ptr end_label = DEC_SUPP(*try_block).end_label;
(ladebug)
stopped at [void walk_try_block_statement(a_statement&):295 0x6ff9fdbc]
    295     an_me_try_block *tb = new an_me_try_block;
(ladebug) ex try_block
0x1405cf881405cfc0
(ladebug) ex *try_block
Error: no value for *try_block
(ladebug) ex stmt
<bad reference>
(ladebug) ex end_label
0x1405cfc01405d530
(ladebug) up
>1  0x6ffb0e4c in walk_statement(stmt={ ... }) /usr/lusers/coleen/decc/src/edg
eg/me_stmt.cxx:1464
   1464         walk_try_block_statement(stmt);
(ladebug) ex stmt
struct {
  dec_supp = 0x0;
  position = struct {
    seq = 6;
    column = 5;
  };
...

the value

	(ladebug) ex try_block
	0x1405cf881405cfc0

strongly suggests this is the pointer/reference size problem that was fixed
in the -26/-27 time frame.

I have volunteered to help Coleen upgrade to -30

/Bevin

Coleen, thanks for helping us identify problems with ladebug.

Bevin, much thanks to you for helping, and all the other problem
notes you have been posting.

..kvs

[Posted by WWW Notes gateway]

I upgraded to -30.

I still get <bad reference> for the stmt
parameter, but the other addresses (like try_block and end_label)
come out correctly now as 32 bit addresses.

This will keep me going at least.

Thanks,
Coleen

Stephen is looking into the cause of <bad reference>.  A better error
message will be displayed if it indeed indicates an error case.

Wanfang

The 5.5 and earlier C++ compilers don't seem to do anything to correctly
describe 32-bit ref's to ladebug.

We have fixed this in 5.6's new debuggen and in 6.0

/Bevin

We need to add this support in ladebug then.

Wanfang

This is considered closed unless it can
be reproduced. This has reference in 885 too.

Thanks,

Subir

Did you try the example in .0?  It's still available.
Did it work correctly?

R.

We believe this has been fixed

() Dennis checked it in

() Matt Hanselman tried out his cases