joe@etac632 (Joe Fulson-Woytek) (05/08/90)
I am trying to debug a large Fortran program. The program ran but the results appeared to indicate a variable was being changed when I wasn't expecting it to be. I thought it was a good opportunity to learn edge/dbx. So I recompiled all the source with -O0 (for no optimization) and -g (for symbols). I then started dbx and got the following message: warning: aux(17) greater than max(16) for file 111 I then got a core dump. If anyone can point me to a meaning for this message, I would greatly appreciate it. Joe Fulson-Woytek
davea@quasar.wpd.sgi.com (David B. Anderson) (05/08/90)
In article <1957@dftsrv.gsfc.nasa.gov>, joe@etac632 (Joe Fulson-Woytek) writes: > I am trying to debug a large Fortran program. The program [ ] > warning: aux(17) greater than max(16) for file 111 > I then got a core dump. If anyone can point me to a meaning for E-mail bounced, so I'm posting. You don't say, but I assume you are still running IRIX release 3.1. Reason: This dbx core dump is most suggestive of an old version of dbx. stdump -n 111 a.out will show you the symbol table for file 111 in a.out. Your file 111 will show just 16 entries in the aux table...... Question: What does the 4 lines of dbx startup say? It should say ``dbx version 1.31'' (plus other stuff). The message means that the aux table (an array of 32-bit unions where data types are recorded) is being probed at a location greater than exists in the (local) aux table for the particular source file. This is nothing you can do anything about :-(. Again: what system version are you using? If you upgraded to 3.2, did you recompile *everything*? As the 3.2 release notes say, dbx cannot deal with objects which have *any* 3.1 object code. Any local libraries in use? Check them! Hope this helps. [ David B. Anderson Silicon Graphics (415)335-1548 davea@sgi.com ] [``What can go wrong?'' --Calvin and Hobbes] PS: This should be handled through the Hotline or e-mail.....Thanks.
joe@etac632 (Joe Fulson-Woytek) (05/09/90)
In article <59528@sgi.sgi.com> davea@quasar.wpd.sgi.com (David B. Anderson) writes: > >E-mail bounced, so I'm posting. > Sorry about that - I have fixed my Reply to line I am running 3.2 and all libraries were recompiled. You gave me a crucial piece of info - the use of the stdump command. It pointed me to a common block which had 2 large arrays in it. By moving one of the arrays out, I was able to enter dbx without any warning messages. Now comes the fun of trying to track my bug. Thanks for the response. Joe Fulson-Woytek