From: Keith Seitz <keiths@redhat.com>
To: Tom Tromey <tom@tromey.com>, Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org, Pedro Alves <palves@redhat.com>
Subject: Re: possible fix for PR symtab/23010
Date: Thu, 24 May 2018 15:54:00 -0000 [thread overview]
Message-ID: <8f477b41-06ba-63a7-716b-0f2f7303da37@redhat.com> (raw)
In-Reply-To: <87lgc91yrf.fsf@tromey.com>
On 05/23/2018 09:08 PM, Tom Tromey wrote:
>>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
>
> Sergio> Keith has performed a few tests today, and it seems that the patch
> Sergio> doesn't fix the real issues reported by Fedora GDB users after all.
> Sergio> I'm still deciding if it makes sense to ship this on Fedora GDB or
> Sergio> not... Sorry for requesting the backport, I hope it's still useful for
> Sergio> GDB 8.1.1.
>
> Maybe the backport is flawed some way. Or did Keith try git master?
> I'm a bit curious to know what fails.
I'm working on git master with the 23010 patch installed. The patch doesn't help with rhbz 1574015 (which I am investigating). Fortunately, this bug has a reproducer.
Keith
next prev parent reply other threads:[~2018-05-24 14:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 19:06 Tom Tromey
2018-04-17 19:17 ` Keith Seitz
2018-04-19 20:39 ` Tom Tromey
2018-04-30 22:44 ` Joel Brobecker
2018-05-07 17:13 ` Joel Brobecker
2018-05-14 19:43 ` Joel Brobecker
2018-05-18 1:22 ` Sergio Durigan Junior
2018-05-24 4:08 ` Tom Tromey
2018-05-24 10:50 ` Sergio Durigan Junior
2018-05-24 10:50 ` Tom Tromey
2018-05-24 15:54 ` Keith Seitz [this message]
2018-05-26 0:24 ` Keith Seitz
2018-05-27 15:20 ` Tom Tromey
2018-05-30 22:26 ` Joel Brobecker
2018-05-17 17:16 ` Tom Tromey
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=8f477b41-06ba-63a7-716b-0f2f7303da37@redhat.com \
--to=keiths@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sergiodj@redhat.com \
--cc=tom@tromey.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