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

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

9756.0. "dbx -> expression too large to evaluate" by TKTVFS::NAGAI_K (katsuya nagai) Thu May 08 1997 08:44

Hello,

Please suggestion me.

I would like to examine the big structure.
The structure is otto_data ( In ATM structure's).
I tried this,

(dbx) px * ( struct otto_data *)0xfffffc00006fee20

expression too large to evaluate
(dbx)

(kdbx)  px * ( struct otto_data *)0xfffffc00006fee20
expression too large to evaluate

What kind of errors ?

		K.Nagai

 



T.RTitleUserPersonal
Name
DateLines
9756.1SMURF::DENHAMDigital UNIX KernelThu May 08 1997 09:373
    Try the same thing using the ladebug debugger, if you have it.
    It will probably work -- ladebug -k. I've seen the same problem in
    dbx and ladebug works around it...
9756.2basically implies the size is larger than 20,000 bytes...QUARRY::petertrigidly defined areas of doubt and uncertaintyThu May 08 1997 13:0720
Dbx uses an internal stack in order to evaluate expressions.  We usually
see this error message when trying to evaluate an array or structure.
In dbx the size of the stack has been fixed (probably at an arbitary
value that was thought to be large enough) at 20,000 bytes.  If the size
of the structure is larger than this, then we get the 
"too big to evaluate" error.  I have an example that routinely gets 
this error because we are looking at an automatic array in fortran
that has not yet been fully set up.  Dbx thinks it is a very large
sized array at the point that it stops, but since dbx stops on the
dimension statement, if it goes one past that, it sees that it is 
actually only an array of one.  I tried the same program in ladebug,
which stops, like dbx on the dimension statement, before the array
is truly set up, and ladebug started printing out all 58000 or so 
elements.  

This is probably worth a QAR.  These days large data arrays and structures
are probably not all that unusual and maybe we should make the stack
dynamic, or grow the stack if need be.

PeterT
9756.3fine!TKTVFS::NAGAI_Kkatsuya nagaiFri May 09 1997 03:0311
Thank's,  quick reply.

We tried to use ladebug.
I can look at needed data.

Thank you so far.