This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Several regressions and we branch soon.


Doug Evans <dje@google.com> writes:

> ... plus lots more for break-interp.exp ...
> FAIL: gdb.base/default.exp: info set
> FAIL: gdb.base/default.exp: show

I can see these two fails in my machine too.

> FAIL: gdb.base/gnu_vector.exp: call add_singlevecs

I see this fail too,
print add_singlevecs((char1) {6}, (int1) {12}, (double1) {24})^M
^M
Program received signal SIGSEGV, Segmentation fault.^M
0x00000000004008ec in add_singlevecs (a=..., b=..., c=...) at ../../../../../binutils-gdb/gdb/testsuite/gdb.base/gnu_vector.c:132^M
132       return (double1) {a[0] + b[0] + c[0]};^M
The program being debugged was signaled while in a function called from GDB.^M
GDB remains in the frame where the signal was received.^M
To change this behavior use "set unwindonsignal on".^M
Evaluation of the expression containing the function^M
(add_singlevecs) will be abandoned.^M
When the function is done executing, GDB will silently stop.^M
(gdb) FAIL: gdb.base/gnu_vector.exp: call add_singlevecs

-- 
Yao (éå)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]