Re: Regressions on i686-pc-linux-gnu

[Markus Deuling <deuling@de.ibm.com>]

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