This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
Re: New unexpected failures with gdb-6.8.50.20081203 in gdb.server/ext-run.exp, gdb.threads/tls.exp on powerpc-linux-gnu.
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: "Anmol P. Paralkar" <b07584 at freescale dot com>
- Cc: gdb-testers at sourceware dot org
- Date: Fri, 5 Dec 2008 21:10:29 +0100
- Subject: Re: New unexpected failures with gdb-6.8.50.20081203 in gdb.server/ext-run.exp, gdb.threads/tls.exp on powerpc-linux-gnu.
- References: <Pine.LNX.4.64.0812031738310.16997@ld0159-tx32>
Hi,
> Target is powerpc-unknown-linux-gnu
> Host is i686-rh73-linux-gnu
in general for remote targets I expect many of the new testcases fail, the
patches are not developed with all the possibilities in mind. It is more
important that no existing testcase turns PASS->FAIL with a new version.
The new FAIL line
+FAIL: gdb.server/ext-run.exp: get process list
is not from me - it is from the patch
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/testsuite/gdb.server/ext-run.exp?cvsroot=src#rev1.2
2008-12-02 Pedro Alves <pedro@codesourcery.com>
Vladimir Prus <vladimir@codesourcery.com>
Implement -list-thread-groups --available
may fail just because your GDB server does not support "qXfer:osdata:read"?
The new FAIL lines
+FAIL: gdb.threads/tls.exp: p a_thread_local
+FAIL: gdb.threads/tls.exp: p file2_thread_local
+FAIL: gdb.threads/tls.exp: p a_thread_local second time
just extend the existing many other FAILs for gdb.threads/tls.exp in your log.
Specifically the line
+FAIL: gdb.threads/tls.exp: p a_thread_local
fails exactly the same like a previous existing FAIL there:
p a_thread_local
Remote connection closed
(gdb) FAIL: gdb.threads/tls.exp: first thread local storage
compared to the new one:
p a_thread_local
Remote connection closed
(gdb) FAIL: gdb.threads/tls.exp: p a_thread_local
Regards,
Jan
On Thu, 04 Dec 2008 01:14:26 +0100, Anmol P. Paralkar wrote:
> Hello,
>
> Between gdb-6.8.50.20081202 and gdb-6.8.50.20081203, we have new unexpected failures
> on target powerpc-linux-gnu (PS: I have not tested on other targets):
>
> --------------------------------------------------------------------------------
> 11787a11788
>> FAIL: gdb.server/ext-run.exp: get process list
> 12315a12317,12321
>> FAIL: gdb.threads/tls.exp: p a_thread_local
>> FAIL: gdb.threads/tls.exp: p file2_thread_local
>> PASS: gdb.threads/tls.exp: info address file2_thread_local
>> FAIL: gdb.threads/tls.exp: p a_thread_local second time
>> PASS: gdb.threads/tls.exp: info address a_thread_local
> 12484,12485c12490,12491
> < # of expected passes 11708
> < # of unexpected failures 94
> ---
>> # of expected passes 11710
>> # of unexpected failures 98
> 12490c12496
> < /proj/.ppc_07/labhome/b07584/gnu/build/gdb-6.8.50.20081202-original/powerpc-linux-gnu-cross/gdb/testsuite/../../gdb/gdb version 6.8.50.20081202 -nw -nx -x /home/b07584/home-armada/gdb-test-infra/daily/perf1vme6-initialize-daily
> ---
>> /proj/.ppc_07/labhome/b07584/gnu/build/gdb-6.8.50.20081203-original/powerpc-linux-gnu-cross/gdb/testsuite/../../gdb/gdb version 6.8.50.20081203 -nw -nx -x /home/b07584/home-armada/gdb-test-infra/daily/perf1vme6-initialize-daily
> --------------------------------------------------------------------------------
>
> I have attached log and summary files for individual runs of ext-run.exp, tls.exp
> for both snapshots. Please let me know if I can help in any other way.
>
> Regards,
> Anmol P. Paralkar
> Freescale Semiconductor.