From: Yao Qi <qiyaoltc@gmail.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Pedro Alves <palves@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>,
Jan Kratochvil <jan.kratochvil@redhat.com>,
Phil Muldoon <pmuldoon@redhat.com>
Subject: Re: [PATCH] Run gdb.compile/*.exp on {x86,x86_64,s390}-linux only
Date: Wed, 17 Jan 2018 10:06:00 -0000 [thread overview]
Message-ID: <CAH=s-POno_0Upt2_CTZfZpCtCHkt2+o0wd3AEo7Dw7jJhyPS+Q@mail.gmail.com> (raw)
In-Reply-To: <87tvvlzl3x.fsf@redhat.com>
On Tue, Jan 16, 2018 at 6:58 PM, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
> Hi Yao,
>
> It seems you found the issue, but just to let you know, there was a
> related (or probably the same?) issue that I fixed a while ago on libcc1
> (GCC counterpart of the "compile" plugin). "compile" wasn't working on
> Debian:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851146
>
> And I submitted a patch to GCC to fix it:
>
> https://gcc.gnu.org/ml/gcc-patches/2017-08/msg01315.html
>
> Which eventually became:
>
> https://gcc.gnu.org/ml/gcc-patches/2017-09/msg00087.html
>
> This is now upstream, but if you're using Ubuntu, you may very well see
> the problem with finding the right GCC compiler.
Hi Sergio,
Yes, that is one issue I've seen before on Ubuntu. I switched to
gcc trunk, then I can run gdb.compile/*.exp tests on Ubuntu.
Thanks!
There is only one fail,
bt^M
#0 _gdb_expr (__regs=0x7ffff7ff3000) at gdb command line:1^M
#1 <function called from gdb>^M
#2 main () at /home/yao.qi/SourceCode/gnu/build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.compile/compile.c:106^M
(gdb) FAIL: gdb.compile/compile.exp: bt
On fedora builder, the test passes,
bt^M
#0 0x00007ffff7ff43f6 in _gdb_expr (__regs=0x7ffff7ff2000) at gdb
command line:1^M
#1 <function called from gdb>^M
#2 main () at /home/gdb-buildbot/fedora-x86-64-1/fedora-x86-64/build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.compile/compile.c:106^M
(gdb) PASS: gdb.compile/compile.exp: bt
I'll fix it in test case.
--
Yao (齐尧)
prev parent reply other threads:[~2018-01-17 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 11:50 Yao Qi
2018-01-16 12:18 ` Pedro Alves
2018-01-16 15:14 ` Yao Qi
2018-01-16 16:47 ` Phil Muldoon
2018-01-16 16:59 ` Pedro Alves
2018-01-16 17:20 ` Pedro Alves
2018-01-16 17:45 ` Yao Qi
2018-01-16 18:58 ` Sergio Durigan Junior
2018-01-17 10:06 ` Yao Qi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH=s-POno_0Upt2_CTZfZpCtCHkt2+o0wd3AEo7Dw7jJhyPS+Q@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.com \
--cc=pmuldoon@redhat.com \
--cc=sergiodj@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox