This is the mail archive of the gdb@sourceware.cygnus.com mailing list for the GDB project. See the GDB home page for more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Date: Wed, 14 Apr 1999 14:13:25 -0700 From: "J. Kean Johnston" <jkj@sco.com> All, below is the result of a test run for GDB 4.18 on SCO OpenServer 5.0.4: There are about 100 failures that still occur with all native configs, such as the ones in member-ptr.exp and overload.exp. However, the following failures are not (for instance) happening on Linux, and should therefore cause you some concern: FAIL: gdb.base/call-rt-st.exp: print print_struct_rep(*struct1, *struct2, *struct3) FAIL: gdb.base/call-rt-st.exp: print print_one_large_struct(*list1) FAIL: gdb.base/call-rt-st.exp: print print_one_double(*d1) FAIL: gdb.base/call-rt-st.exp: print print_two_floats(*f3) FAIL: gdb.base/call-rt-st.exp: print print_bit_flags(*flags) FAIL: gdb.base/call-rt-st.exp: print print_bit_flags_combo(*flags_combo) FAIL: gdb.base/call-rt-st.exp: print print_three_chars(*three_char) FAIL: gdb.base/call-rt-st.exp: print print_five_chars(*five_char) FAIL: gdb.base/call-rt-st.exp: print print_int_char_combo(*int_char_combo) FAIL: gdb.base/callfuncs.exp: p t_float_values(3.14159,-2.3765) FAIL: gdb.base/callfuncs.exp: p t_float_values(float_val1,float_val2) FAIL: gdb.base/callfuncs.exp: p t_float_values(3.14159,float_val2) FAIL: gdb.base/callfuncs.exp: p t_float_values(float_val1,-2.3765) FAIL: gdb.base/callfuncs2.exp: p t_float_values(3.14159,-2.3765) FAIL: gdb.base/callfuncs2.exp: p t_float_values(float_val1,float_val2) FAIL: gdb.base/callfuncs2.exp: p t_float_values(3.14159,float_val2) FAIL: gdb.base/callfuncs2.exp: p t_float_values(float_val1,-2.3765) FAIL: gdb.base/langs.exp: up to foo in langs.exp FAIL: gdb.base/langs.exp: show language at foo in langs.exp FAIL: gdb.base/langs.exp: up to cppsub_ in langs.exp FAIL: gdb.base/langs.exp: show language at cppsub_ in langs.exp FAIL: gdb.base/langs.exp: up to fsub in langs.exp FAIL: gdb.base/langs.exp: show language at fsub in langs.exp FAIL: gdb.base/maint.exp: maint print psymbols FAIL: gdb.base/maint.exp: maint print msymbols FAIL: gdb.base/maint.exp: maint print symbols FAIL: gdb.base/signals.exp: next to handler in signals_tests_1 FAIL: gdb.base/signals.exp: backtrace in signals_tests_1 FAIL: gdb.base/signals.exp: continue to handler: the program exited FAIL: gdb.base/signals.exp: p count #1 in signals.exp FAIL: gdb.base/signals.exp: p func1 () #2 in signals.exp FAIL: gdb.base/signals.exp: bt in signals.exp FAIL: gdb.base/signals.exp: continue in signals.exp: the program exited FAIL: gdb.base/signals.exp: p count #2 in signals.exp FAIL: gdb.base/signals.exp: signal without arguments disallowed FAIL: gdb.base/signals.exp: sent signal 5 FAIL: gdb.base/so-impl-ld.exp: implicit solibs tests suppressed FAIL: gdb.base/so-impl-ld.exp: step over solib call FAIL: gdb.base/so-impl-ld.exp: step into solib call FAIL: gdb.base/so-impl-ld.exp: step in solib call FAIL: gdb.base/so-impl-ld.exp: step out of solib call FAIL: gdb.base/step-test.exp: stepi: finish call FAIL: gdb.base/step-test.exp: nexti over function FAIL: gdb.base/step-test.exp: run to pass large struct: the program is no longer running FAIL: gdb.base/step-test.exp: large struct by value: the program is no longer running FAIL: gdb.base/step-test.exp: run to finish: the program is no longer running FAIL: gdb.base/varargs.exp: print find_max_double(5,1.0,17.0,2.0,3.0,4.0) This pattern of failures doesn't suggest anything obvious to me, so you may be hitting a combination of problems. Some of these failures tend to be associated with bad debug info from the compiler - which compiler are you using? Stan