drs@bnlux0.bnl.gov (David R. Stampf) (02/21/90)
A friend of mine who does not have access to the net is having a *lot* of problems with fortran and dbx on a sparcstation. The program is fairly big, and while dbx will *run* the program, it cannot set breakpoints in subroutines (complains about a bad address 0x0 and suggests that you may be running the program more than once - he isn't) and "stepping" is more like "nexting" - you do not step into subroutines. The system is 4.03c. I have seen postings here in the past complaining about fortran and dbx but never an indication that a fix was found, nor that Sun acked the problem. Thanks for any info you can provide. < dave stampf (for jim niederer)
poffen@sj.ate.slb.com (Russ Poffenberger) (03/02/90)
In article <5188@brazos.Rice.edu> drs@bnlux0.bnl.gov (David R. Stampf) writes: >X-Sun-Spots-Digest: Volume 9, Issue 47, message 18 > >A friend of mine who does not have access to the net is having a *lot* of >problems with fortran and dbx on a sparcstation. The program is fairly >big, and while dbx will *run* the program, it cannot set breakpoints in >subroutines (complains about a bad address 0x0 and suggests that you may >be running the program more than once - he isn't) and "stepping" is more >like "nexting" - you do not step into subroutines. The system is 4.03c. I am not sure about specific fortran problems, but there is a patch from sun that fixes LOTS of dbx bugs. Call your Sun rep and request patch # 100042 Here is a list of bug reports the patch addresses 1001701 # dbx and dbxtool die when given a bad expression to print 1002772 # dbx gives erroneous "not a field" error messages 1004495 # can't print Pascal array element, if pointed to, in dbx 1004650 # "dbx" on a "core" file doesn't indicate signal info 1006513 # dbxtool coredumps on right mouse key event 1007217 # undisplay does not work right with dbx 1008902 # dbxtool: strlen function messes up tty echo mode 1008926 # "trace" and "tracei" don't work in "dbx" 1009050 # cc -o option confuses dbx 1009175 # Invoke the textedit within the dbx gets error message. 1009178 # dbxtool puts corrupted file names in top window 1009510 # dbx won't work if any nfs mounts are 'stale' 1010276 # print, dbx crashes 1010502 # dbx doesn't deal with object files with multiple N_SO entries 1010676 # dbxtool dies on printing void functions 1010892 # dbx(tool) gives warnings when displaying function stack 1011104 # print, seg violation, core dump 1011129 # dbx help lines are syntactically incorrect 1011142 # dbx step command different on sun3 and sun4 1011270 # "list" command in dbxtool with no current program core dumps 1011309 # whatis, dbx cmd interp. crashes 1011356 # printing an address in dbx using the "g"& "E" mode gives error 1011429 # Fortran do loop causes dbx to print garbage values on sun4 1011484 # In 'dbx', a 'stop <line-number>' causes all stops to be ignored 1011532 # sporadic ability in finding source files 1011666 # dbx does not display bit fields in structures correctly 1011713 # next and step can't step over fp branches on Sun-4 1011733 # dbx does not always apply USE-path when searching for source 1011769 # dbx dumps core when printing Pascal record objects 1011788 # in dbx, source ~filename => segmentation fault 1011848 # dbx gives incorrect value for string field value in structure 1011854 # dbx cannot read core file under shared libraries 1011943 # dbx limits nested include files to 10,gives "lookaside" error 1011991 # dbx -r option broken for f77 1012437 # cannot set variable to enum value 1012439 # setting variable to enum constant causes dbx internal error 1012495 # attempt to use hex address as pointer causes dbx to abort 1012500 # Corrupt stab info for enum causes internal error 1012530 # file cmd with nonexistent file & wildcard => segmentation fault 1012552 # dbx prints garbage error messages when {cont at xx;} is used 1012617 # Dbx's "cont at" command fails on a sun4 1012765 # dbx f77 prog compiled in 2 passes, stages, can't see source file 1012766 # dbx f77 fortran prog calls MAX step/next go to end 1012842 # dbxtool dies on printing void functions 1012941 # 4.0 dbx can't print Pascal char values directly 1013647 # Sun4 dbx bus error when told to stop at nonexistent line 1013648 # dbx dumps core if run command uses backquoted cmd with spaces 1013694 # Dbxtool allows editing of read-only files. 1013749 # dbx crashes when dereferencing through 2 ptrs. during set 1013951 # 386 dbx does not allow function names over 23 characters 1013952 # 386 dbx dumps core if no source found 1013982 # 4.0.1 fix for bug 1011429 has broken dbx in a new way 1014049 # dbx reports SEG VIOL on second call to shared lib routine 1014114 # 4.0 dbx confuses file statics and globals 1014378 # dbx command "trace expr at lineno" is broken 1014550 # dbx internal error when def'n with a forward ref is in separate file 1014618 # dbxtool crashes because of core file 1014933 # dbx complains about .c file is .o file is renamed 1015042 # 386i dbx "stop in" always displays last Pascal routine compiled 1015077 # sun386i dbxtool -Wi produces empty window 1015086 # 386i dbx aborts when no read permission on NFS-mounted source 1015156 # dbx is not recoginizing variable names with "$" 1015180 # dbx(tool) does not work properly with multiple pascal files. 1015271 # 386i dbxtool doesn't resize properly 1015283 # dbx does not print or set C bitfields that are 24 bits long. 1015287 # dbx favors C objects over Pascal objects of same name 1015300 # dbx does not support source level debugging for shared objects 1015389 # i386 $esp register incorrect, $bp, $sp, $$ip should be hex 1015601 # 386i debugger can not follow soft links in debugging programs 1015611 # dbx does not print records or variant records in a readable format 1016172 # dbx print functions incorrectly 1016174 # debug, can't attach to process 1016341 # sun386i dbx E (extended) format doesn't work on $st0 - $st7 1016371 # sun386i register display has miscellaneous problems 1016374 # 4.0 386i dbx doesn't display 387 registers properly 1017095 # dbx gets confused over two static variables with same name 1017244 # dbx fails to deal with N_SOL stab entries correctly 1017275 # dbx clear command doesn't clear breakpoint 1017437 # 386i dbx cannot display values of FORTRAN COMMON objects 1017523 # dbx core dumps when reference to undefined shell variable is made 1017644 # Dbxtool dumps core while parsing an incorrectly formed "use" command 1018008 # "dbxenv case insensitive" command disallows uppercase modes 1018080 # 4.0 dbx will not run in background 1018237 # dbx status doesn't display "in <proc>" part of trace command 1018261 # setenv command in dbxtool does not work 1018397 # dbx removes all breakpoints each time an executable is reread 1018563 # problem w/ nesting pascal prog, loses line# then regains it 1018598 # dbx sigsegv's when attempting to print expression 1018866 # sun368 dbx stacktrace (where cmd) prints extra parameter and _start() 1019143 # run dbx; run exits dbx w/ allocated string table too small 1019631 # dbxtool help pwd gets 'syntax error on "pwd"' 1019710 # Sun-4 dbx dumps core when asked to display register %g0 1019912 # Dbx dies if there is a stale NFS mount 1019932 # dbx fails on continuation lines of stabs in shared objects 1019996 # dbx print or call fopen(arg, arg) broken on sun4. okay on sun-3. 1020097 # dbx no longer complains if source file is newer than executable 1020192 # unable to print mixed types of boolean and numeric 1020219 # pascal 2.0's dbx on 386i fails with doubly-nested procedures 1020341 # dbxtool core dumps in run command 1020375 # dbx can't handle filenames with embedded dots 1021027 # dbx, doesn't recognize -g compile Russ Poffenberger DOMAIN: poffen@sj.ate.slb.com Schlumberger Technologies UUCP: {uunet,decwrl,amdahl}!sjsca4!poffen 1601 Technology Drive CIS: 72401,276 San Jose, Ca. 95110 (408)437-5254