Regressions on i686-pc-linux-gnu

Regressions on i686-pc-linux-gnu

[Markus Deuling]

Hi,

I posted my testresults for i686-pc-linux-gnu to gdb-testers@sourceware.org. Unfortunately http://sourceware.org/ml/gdb-testresults/2008-01/
doesn't seem to take notice of it :-( Hence I added the testresults to the bottom of this mail.

I see 165 FAILs compared to around 15 from beginning of december 2007. Is anyone else seeing this?

Regards,
Markus


Testresults:

Native configuration is i686-pc-linux-gnu

        === gdb tests ===


Running target unix
FAIL: gdb.base/call-strs.exp: print str_func1(s)
FAIL: gdb.base/call-strs.exp: print str_func1("test string")
FAIL: gdb.base/call-strs.exp: call str_func1(s)
FAIL: gdb.base/call-strs.exp: call str_func1("test string")
FAIL: gdb.base/call-strs.exp: print str_func1(buf)
FAIL: gdb.base/call-strs.exp: call str_func1(buf)
FAIL: gdb.base/call-strs.exp: print str_func("a","b","c","d","e","f","g")
FAIL: gdb.base/call-strs.exp: call str_func("a","b","c","d","e","f","g")
FAIL: gdb.base/call-strs.exp: print str_func(s,s,s,s,s,s,s)
FAIL: gdb.base/call-strs.exp: call str_func(s,s,s,s,s,s,s)
FAIL: gdb.base/checkpoint.exp: restart 2 one
FAIL: gdb.base/checkpoint.exp: step in 2 one
FAIL: gdb.base/checkpoint.exp: verify i 2 one
FAIL: gdb.base/checkpoint.exp: verify lines 2 one
FAIL: gdb.base/checkpoint.exp: restart 3 one
FAIL: gdb.base/checkpoint.exp: step in 3 one
FAIL: gdb.base/checkpoint.exp: verify i 3 one
FAIL: gdb.base/checkpoint.exp: verify lines 3 one
FAIL: gdb.base/checkpoint.exp: restart 4 one
FAIL: gdb.base/checkpoint.exp: step in 4 one
FAIL: gdb.base/checkpoint.exp: verify i 4 one
FAIL: gdb.base/checkpoint.exp: verify lines 4 one
FAIL: gdb.base/checkpoint.exp: restart 5 one
FAIL: gdb.base/checkpoint.exp: step in 5 one
FAIL: gdb.base/checkpoint.exp: verify i 5 one
FAIL: gdb.base/checkpoint.exp: verify lines 5 one
FAIL: gdb.base/checkpoint.exp: restart 6 one
FAIL: gdb.base/checkpoint.exp: step in 6 one
FAIL: gdb.base/checkpoint.exp: verify i 6 one
FAIL: gdb.base/checkpoint.exp: verify lines 6 one
FAIL: gdb.base/checkpoint.exp: restart 7 one
FAIL: gdb.base/checkpoint.exp: step in 7 one
FAIL: gdb.base/checkpoint.exp: verify i 7 one
FAIL: gdb.base/checkpoint.exp: verify lines 7 one
FAIL: gdb.base/checkpoint.exp: restart 8 one
FAIL: gdb.base/checkpoint.exp: step in 8 one
FAIL: gdb.base/checkpoint.exp: verify i 8 one
FAIL: gdb.base/checkpoint.exp: verify lines 8 one
FAIL: gdb.base/checkpoint.exp: restart 9 one
FAIL: gdb.base/checkpoint.exp: step in 9 one
FAIL: gdb.base/checkpoint.exp: verify i 9 one
FAIL: gdb.base/checkpoint.exp: verify lines 9 one
FAIL: gdb.base/checkpoint.exp: restart 10 one
FAIL: gdb.base/checkpoint.exp: step in 10 one
FAIL: gdb.base/checkpoint.exp: verify i 10 one
FAIL: gdb.base/checkpoint.exp: verify lines 10 one
FAIL: gdb.base/checkpoint.exp: restart 0 one
FAIL: gdb.base/checkpoint.exp: break3 one
FAIL: gdb.base/checkpoint.exp: restart 1 two
FAIL: gdb.base/checkpoint.exp: breakpoint 1 1 one
FAIL: gdb.base/checkpoint.exp: step in 1 two
FAIL: gdb.base/checkpoint.exp: verify lines 1 two
FAIL: gdb.base/checkpoint.exp: restart 2 two
FAIL: gdb.base/checkpoint.exp: breakpoint 1 2 one
FAIL: gdb.base/checkpoint.exp: step in 2 two
FAIL: gdb.base/checkpoint.exp: verify lines 2 two
FAIL: gdb.base/checkpoint.exp: restart 3 two
FAIL: gdb.base/checkpoint.exp: breakpoint 1 3 one
FAIL: gdb.base/checkpoint.exp: step in 3 two
FAIL: gdb.base/checkpoint.exp: verify lines 3 two
FAIL: gdb.base/checkpoint.exp: restart 4 two
FAIL: gdb.base/checkpoint.exp: breakpoint 1 4 one
FAIL: gdb.base/checkpoint.exp: step in 4 two
FAIL: gdb.base/checkpoint.exp: verify lines 4 two
FAIL: gdb.base/checkpoint.exp: restart 5 two
FAIL: gdb.base/checkpoint.exp: breakpoint 1 5 one
FAIL: gdb.base/checkpoint.exp: step in 5 two
FAIL: gdb.base/checkpoint.exp: verify lines 5 two
FAIL: gdb.base/checkpoint.exp: restart 6 two
FAIL: gdb.base/checkpoint.exp: breakpoint 1 6 one
FAIL: gdb.base/checkpoint.exp: step in 6 two
FAIL: gdb.base/checkpoint.exp: verify lines 5 two
FAIL: gdb.base/checkpoint.exp: restart 7 two
FAIL: gdb.base/checkpoint.exp: breakpoint 1 7 one
FAIL: gdb.base/checkpoint.exp: step in 7 two
FAIL: gdb.base/checkpoint.exp: verify lines 7 two
FAIL: gdb.base/checkpoint.exp: restart 0 one
FAIL: gdb.base/checkpoint.exp: break4 one
FAIL: gdb.base/checkpoint.exp: delete copy1
FAIL: gdb.base/checkpoint.exp: restart 1 three
FAIL: gdb.base/checkpoint.exp: break2 1 one
FAIL: gdb.base/checkpoint.exp: outfile still open 1
FAIL: gdb.base/checkpoint.exp: restart 1 three
FAIL: gdb.base/checkpoint.exp: break2 2 one
FAIL: gdb.base/checkpoint.exp: outfile still open 2
FAIL: gdb.base/checkpoint.exp: restart 1 three
FAIL: gdb.base/checkpoint.exp: break2 3 one
FAIL: gdb.base/checkpoint.exp: outfile still open 3
FAIL: gdb.base/checkpoint.exp: restart 1 three
FAIL: gdb.base/checkpoint.exp: break2 4 one
FAIL: gdb.base/checkpoint.exp: outfile still open 4
FAIL: gdb.base/checkpoint.exp: restart 1 three
FAIL: gdb.base/checkpoint.exp: break2 5 one
FAIL: gdb.base/checkpoint.exp: outfile still open 5
FAIL: gdb.base/checkpoint.exp: restart 1 three
FAIL: gdb.base/checkpoint.exp: break2 6 one
FAIL: gdb.base/checkpoint.exp: outfile still open 6
FAIL: gdb.base/checkpoint.exp: restart 1 three
FAIL: gdb.base/checkpoint.exp: break2 7 one
FAIL: gdb.base/checkpoint.exp: outfile still open 7
FAIL: gdb.base/checkpoint.exp: restart 1 three
FAIL: gdb.base/checkpoint.exp: break2 8 one
FAIL: gdb.base/checkpoint.exp: outfile still open 8
FAIL: gdb.base/checkpoint.exp: restart 1 three
FAIL: gdb.base/checkpoint.exp: break2 9 one
FAIL: gdb.base/checkpoint.exp: outfile still open 9
FAIL: gdb.base/checkpoint.exp: restart 1 three
FAIL: gdb.base/checkpoint.exp: break2 10 one
FAIL: gdb.base/checkpoint.exp: outfile still open 10
FAIL: gdb.base/checkpoint.exp: Exit, dropped into next fork one
FAIL: gdb.base/checkpoint.exp: Exit, dropped into next fork two
FAIL: gdb.base/checkpoint.exp: Exit, dropped into next fork three
FAIL: gdb.base/checkpoint.exp: Exit, dropped into next fork four
FAIL: gdb.base/checkpoint.exp: Exit, dropped into next fork five
FAIL: gdb.base/corefile.exp: accessing mmapped data in core file (mapping address not found in core file)
FAIL: gdb.base/define.exp: test ifnospace is parsed correctly
FAIL: gdb.base/define.exp: test whilenospace is parsed correctly
FAIL: gdb.base/define.exp: use hook-stop command
XPASS: gdb.base/interrupt.exp: send end of file
FAIL: gdb.base/shlib-call.exp: print shr1(1)
FAIL: gdb.base/shlib-call.exp: print shr1(g)
FAIL: gdb.base/shlib-call.exp: run until breakpoint set at a function
FAIL: gdb.base/shlib-call.exp: print shr1(1) 2nd time
FAIL: gdb.base/shlib-call.exp: print  mainshr1(1) from shlib func
FAIL: gdb.base/shlib-call.exp: step out of shr2
FAIL: gdb.base/shlib-call.exp: print  mainshr1(1) from main
FAIL: gdb.base/shlib-call.exp: step into mainshr1
FAIL: gdb.base/store.exp: continue field 2
FAIL: gdb.base/store.exp: next field 2
FAIL: gdb.base/store.exp: old field 2
FAIL: gdb.base/store.exp: new field 2
FAIL: gdb.base/store.exp: f_2.i
FAIL: gdb.base/store.exp: f_2.j
FAIL: gdb.base/store.exp: f_2.k
FAIL: gdb.base/store.exp: F_2.i
FAIL: gdb.base/store.exp: F_2.j
FAIL: gdb.base/store.exp: F_2.k
FAIL: gdb.base/store.exp: continue field 3
FAIL: gdb.base/store.exp: next field 3
FAIL: gdb.base/store.exp: old field 3
FAIL: gdb.base/store.exp: F_3.i
FAIL: gdb.base/store.exp: F_3.j
FAIL: gdb.base/store.exp: F_3.k
FAIL: gdb.base/store.exp: continue field 4
FAIL: gdb.base/store.exp: next field 4
FAIL: gdb.base/store.exp: old field 4
FAIL: gdb.base/store.exp: F_4.i
FAIL: gdb.base/store.exp: F_4.k
FAIL: gdb.cp/annota3.exp: annotate-quit (pattern 1)
FAIL: gdb.cp/arg-reference.exp: No false reference
FAIL: gdb.cp/inherit.exp: ptype tagless struct
FAIL: gdb.cp/inherit.exp: print type of anonymous union // unrecognized line type 1: class_with_anon_union::._0;
FAIL: gdb.cp/namespace.exp: print 'F::cXf'
FAIL: gdb.cp/namespace.exp: print F::cXf
FAIL: gdb.cp/namespace.exp: print F::cXfX
FAIL: gdb.cp/namespace.exp: print 'G::Xg'
FAIL: gdb.cp/namespace.exp: print G::Xg
FAIL: gdb.cp/namespace.exp: print G::XgX
FAIL: gdb.cp/namespace.exp: print cXOtherFile
FAIL: gdb.cp/namespace.exp: print XOtherFile
FAIL: gdb.dwarf2/dw2-ranges.exp: info line func
WARNING: Testcase compile failed, so some tests in this file will automatically fail.
ERROR: /home/deuling/gdb/dev/build/gdb/testsuite/../../gdb/insight does not exist.
ERROR: gdbtk_start
ERROR: /home/deuling/gdb/dev/build/gdb/testsuite/../../gdb/insight does not exist.
ERROR: gdbtk_start
WARNING: Testcase compile failed, so some tests in this file will automatically fail.
ERROR: /home/deuling/gdb/dev/build/gdb/testsuite/../../gdb/insight does not exist.
ERROR: gdbtk_start
ERROR: /home/deuling/gdb/dev/build/gdb/testsuite/../../gdb/insight does not exist.
ERROR: gdbtk_start
ERROR: /home/deuling/gdb/dev/build/gdb/testsuite/../../gdb/insight does not exist.
ERROR: /home/deuling/gdb/dev/build/gdb/testsuite/../../gdb/insight does not exist.
ERROR: /home/deuling/gdb/dev/build/gdb/testsuite/../../gdb/insight does not exist.
ERROR: gdbtk_start
ERROR: gdbtk_start
ERROR: gdbtk_start
ERROR: /home/deuling/gdb/dev/build/gdb/testsuite/../../gdb/insight does not exist.
ERROR: gdbtk_start
UNRESOLVED: gdb.java/jmain.exp: Couldn't compile /home/deuling/gdb/dev/gdb/testsuite/gdb.java/jmain.java
FAIL: gdb.server/server-run.exp: continue to main
FAIL: gdb.threads/pthreads.exp: check backtrace from main thread
FAIL: gdb.threads/staticthreads.exp: running to main in runto
FAIL: gdb.threads/staticthreads.exp: Continue to main's call of sem_post
FAIL: gdb.threads/staticthreads.exp: handle SIG32 helps

        === gdb Summary ===

# of expected passes        11706
# of unexpected failures    165
# of unexpected successes    1
# of expected failures        43
# of unknown successes        6
# of known failures        42
# of unresolved testcases    1
# of untested testcases        7
# of unsupported tests        37
/home/deuling/gdb/dev/build/gdb/testsuite/../../gdb/gdb version  6.7.50.20080109-cvs -nx


Compiler version: 6.7.50.20080109-cvs -nx gdb Platform: i686-pc-linux-gnu

EOF

Re: Regressions on i686-pc-linux-gnu

[Daniel Jacobowitz]

On Wed, Jan 09, 2008 at 04:23:24PM +0100, Markus Deuling wrote:
> Hi,
>
> I posted my testresults for i686-pc-linux-gnu to
> gdb-testers@sourceware.org. Unfortunately
> http://sourceware.org/ml/gdb-testresults/2008-01/ doesn't seem to
> take notice of it :-( Hence I added the testresults to the bottom of
> this mail.

Those are two different mailing lists.

Did your system C library or compiler change?  What does the first new
failure look like in gdb.log?


-- 
Daniel Jacobowitz
CodeSourcery

Re: Regressions on i686-pc-linux-gnu

[Markus Deuling]

Daniel Jacobowitz schrieb:

>> I posted my testresults for i686-pc-linux-gnu to
>> gdb-testers@sourceware.org. Unfortunately
>> http://sourceware.org/ml/gdb-testresults/2008-01/ doesn't seem to
>> take notice of it :-( Hence I added the testresults to the bottom of
>> this mail.
> 
> Those are two different mailing lists.

Ah, you're right :-) I looked at the wrong website. This link is the correct one
http://sourceware.org/ml/gdb-testers/2008-q1/msg00000.html


Why do we have
http://sourceware.org/ml/gdb-testers/
and
http://sourceware.org/ml/gdb-testresults/
?

> 
> Did your system C library or compiler change?  What does the first new
> failure look like in gdb.log?

Yes, I switched my distro (glibc 2.5.-18, gcc 4.1.2)
This one is the first new FAIL:

print  str_func1(s)^M
^M
Program received signal SIGTRAP, Trace/breakpoint trap.^M
str_func1 (s1="test string") at /home/deuling/gdb/dev/gdb/testsuite/gdb.base/call-strs.c:15^M
15      {^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 (str_func1) will be abandoned.^M
(gdb) FAIL: gdb.base/call-strs.exp: print str_func1(s)
print  str_func1("test string")^M

I see more of this kind also in checkpoint.exp etc.



Regards,
Markus

Re: Regressions on i686-pc-linux-gnu

[Daniel Jacobowitz]

On Wed, Jan 09, 2008 at 05:36:54PM +0100, Markus Deuling wrote:
> Why do we have
> http://sourceware.org/ml/gdb-testers/
> and
> http://sourceware.org/ml/gdb-testresults/
> ?

No clue.

>> Did your system C library or compiler change?  What does the first new
>> failure look like in gdb.log?
>
> Yes, I switched my distro (glibc 2.5.-18, gcc 4.1.2)
> This one is the first new FAIL:
>
> print  str_func1(s)^M
> ^M
> Program received signal SIGTRAP, Trace/breakpoint trap.^M
> str_func1 (s1="test string") at /home/deuling/gdb/dev/gdb/testsuite/gdb.base/call-strs.c:15^M

Looks to me like this is a bunk kernel.  I know there was a recent x86
kernel release with this error.

-- 
Daniel Jacobowitz
CodeSourcery

Re: Regressions on i686-pc-linux-gnu

[Markus Deuling]

Daniel Jacobowitz schrieb:
>>> Did your system C library or compiler change?  What does the first new
>>> failure look like in gdb.log?
>> Yes, I switched my distro (glibc 2.5.-18, gcc 4.1.2)
>> This one is the first new FAIL:
>>
>> print  str_func1(s)^M
>> ^M
>> Program received signal SIGTRAP, Trace/breakpoint trap.^M
>> str_func1 (s1="test string") at /home/deuling/gdb/dev/gdb/testsuite/gdb.base/call-strs.c:15^M
> 
> Looks to me like this is a bunk kernel.  I know there was a recent x86
> kernel release with this error.
> 

Your're right. I updated my kernel to a newer version and the testsuite run looks good again. Thank you
very much for pointing me to that !

Regards,
Markus