Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Nick Clifton <nickc@redhat.com>
Cc: gdb-buildbot@sergiodj.net, gdb-patches@sourceware.org
Subject: Re: Oh dear. I regret to inform you that commit 053af8c9034f92d6e36a1180655ba22a65c56437 might be unfortunate
Date: Tue, 08 Jan 2019 14:29:00 -0000	[thread overview]
Message-ID: <d252740535f3a682fd232cc1fdb6e88a@polymtl.ca> (raw)
In-Reply-To: <dc71bd35-b08d-cbd4-f77b-7ba1907a6065@redhat.com>

On 2019-01-08 06:24, Nick Clifton wrote:
> Hi Simon,
> 
>>> As you can see, GDB needs to be adjusted to stop using
> 
> Sorry - I totally forgot to check the effect that the change would
> have on GDB.  Mea culpa.
> 
>>> test it, get it reviewed).  Would you mind reverting this patch, just
>>> the time we adjust the GDB code?
> 
> Not at all.  In fact I see that you have now done so.
> 
>> I ended up reverting this patch to unbreak the build.  I'll try to 
>> update the GDB code shortly to unblock it (or if somebody else is 
>> motived, I don't mind).
>> 
>> When re-syncing the code with GCC, note that there are corresponding 
>> changes to include/demangle.h that should be imported too.
> 
> Yes, I missed that too. :-(  There is also an update to the
> binutils/testsuite/binutils-all/cxxfilt.exp file that needs to go in
> to fix the tests for targets that use an
> underscore prefix to their symbol names.   Also, once demangle.h is
> synchronized the
> binutils/cxxfilt.c source file will fail to build because it checks
> for redacted demangling
> styles.  I have patches locally to fix both of these problems, which I
> can supply to
> a committer or else check in myself.

Ok, thanks for the update.

You can check in the binutils bits right now if you want.

Simon


  reply	other threads:[~2019-01-08 14:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 13:26 gdb-buildbot
2019-01-07 13:26 ` Breakage on builder Debian-s390x-native-extended-gdbserver-m64, revision 053af8c9034f92d6e36a1180655ba22a65c56437 gdb-buildbot
2019-01-07 13:26 ` Breakage on builder RHEL-s390x-m64, " gdb-buildbot
2019-01-07 13:29 ` Breakage on builder Solaris11-sparcv9-m64, " gdb-buildbot
2019-01-07 13:29 ` Breakage on builder Debian-s390x-native-gdbserver-m64, " gdb-buildbot
2019-01-07 13:31 ` Breakage on builder Fedora-i686, " gdb-buildbot
2019-01-07 13:31 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-01-07 13:31 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-01-07 13:31 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-01-07 13:33 ` Breakage on builder Debian-s390x-m64, " gdb-buildbot
2019-01-07 13:34 ` Breakage on builder Solaris11-amd64-m64, " gdb-buildbot
2019-01-07 13:38 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2019-01-07 13:40 ` Breakage on builder NetBSD-x86_64-m64, " gdb-buildbot
2019-01-07 13:40 ` Breakage on builder Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2019-01-07 13:40 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2019-01-07 13:40 ` Breakage on builder Fedora-x86_64-w64-mingw32, " gdb-buildbot
2019-01-07 13:43 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot
2019-01-08  6:53 ` Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot
2019-01-08  7:02 ` Breakage on builder Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2019-01-08  7:11 ` Breakage on builder Ubuntu-Aarch64-m64, " gdb-buildbot
     [not found] ` <c9d33a75a00d4ceb8e126a1dbcbcb16c@polymtl.ca>
     [not found]   ` <3f3e538c74685b15579bf913aa764067@polymtl.ca>
2019-01-08 11:25     ` Oh dear. I regret to inform you that commit 053af8c9034f92d6e36a1180655ba22a65c56437 might be unfortunate Nick Clifton
2019-01-08 14:29       ` Simon Marchi [this message]
2019-01-08 16:54         ` Nick Clifton
2019-01-09 18:09           ` Simon Marchi
2019-01-10  9:48             ` Nick Clifton

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=d252740535f3a682fd232cc1fdb6e88a@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-buildbot@sergiodj.net \
    --cc=gdb-patches@sourceware.org \
    --cc=nickc@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