dhekne@ncst.ernet.in (Dhekne c/o NCST) (09/07/90)
Hello !! I have been trying to use the debugger on IRIS 3130, 'edge'. But I am unable to. Whenever I use it on non-graphics programs, it is OK, but for graphic programs, it starts behaving funny. Mainly, it just exits from the program or gets stuck. This is the case with 'dbx' also. However, I have found that it works in some cases - When you are using single buffer mode, and no popup menus. The moment you use either double buffer mode or popup menus, it starts giving problem. Actually it works till the point you have set the break point, and on reaching it, it exits. Has anybody faced such a problem ? Is there any solution ? We are looking at the possibilities of upgrading 3130 to 4d/20. Is the 4d/20 faster than 3130, or it is just a cheaper version of the higher 4d models ? Does it contain any geometric engines ? ( the technical details of 4d/20 do not say anything about them ). How do the users rate 4d/20 in comparison with 3130 ? (questions ! questions !!) suggestions ? help ? THANKS !! Sunil Kulkarni ( dhekne@shakti.ernet.in )
blbates@AERO4.LARC.NASA.GOV ("Brent L. Bates AAD/TAB MS361 x42854") (09/08/90)
Edge on the 3130 doesn't work with graphics, period. However,
dbx does work on the 3130, sort of. One of the main things you must
do in a graphics program is to have a call to foreground before opening
a window or dbx wont work.
If you can afford to up grade to a SGI Personal Iris do it.
SGI never supported the 3130 from the beginning, so most of the software
bugs were never fixed. The window manager, MEX, will crash if you
sneeze, and there are a whole list of other problems.
--
Brent L. Bates
NASA-Langley Research Center
M.S. 361
Hampton, Virginia 23665-5225
(804) 864-2854
E-mail: blbates@aero4.larc.nasa.gov or blbates@aero2.larc.nasa.gov