public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: gdb-7.11.1 - 2 weeks to go...
Date: Thu, 19 May 2016 15:21:00 -0000	[thread overview]
Message-ID: <395c33b0-7071-ed80-915a-dd8dbefe2786@redhat.com> (raw)
In-Reply-To: <20160510161756.GB26324@adacore.com>

On 05/10/2016 05:17 PM, Joel Brobecker wrote:
> Hello everyone,
> 
> Just a quick update on this 7.11.1 release - our target release date
> is about 2 weeks away. As far as I can tell from looking at...
> 
>     https://sourceware.org/gdb/wiki/GDB_7.11_Release
> 
> ... we have 2 open PRs:
> 
>   * Bug 19828 - 7.11 regression: non-stop gdb -p <process from a
>     container>: internal error
> 
>     Looks already fixed on master, so there is a chance we might
>     be able to fix that on the branch soon.
> 

Odd, it definitely doesn't work for me on master.

This is the one that I said in the other status thread that I had
a patch for, but that it surprisingly caused regressions in
the attach-many-short-lived-threads.exp testcase.

I finally managed to find some time to stare at "set debug infrun"
logs, and wrote (I think) a full fix, here:

 [PATCH 0/6] Fix PR gdb/19828 (attach -> internal error) and attach optimizations
 https://sourceware.org/ml/gdb-patches/2016-05/msg00335.html

That's a bit ... invasive ...

I have a simpler version too, which is being carried by Fedora for
a few weeks without reports of problems:

 [PATCH/7.11.1?] Simpler fix PR gdb/19828: gdb -p <process from a container>: internal error
 https://sourceware.org/ml/gdb-patches/2016-05/msg00335.html

... though that's not as comprehensive as the bigger series.
It leaves "attach&" (background attach) broken...  I haven't heard
complaints about that so far; maybe nobody uses that command...

Another option that just occurred to me, is to apply the fuller fix
to the branch (patch #6 in the series), and disable the
attach-many-short-lived-threads.exp test in the branch?  GDB regresses
in the use case of attaching to a program that is constantly spawning
many threads in quick succession, though that's a contrived use case
to expose problems.  Probably no program in the wild is like that.
I hope.  Use cases like Go programs with tons of goroutines make me
worry a bit.

Thanks,
Pedro Alves

  reply	other threads:[~2016-05-19 15:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 16:18 Joel Brobecker
2016-05-19 15:21 ` Pedro Alves [this message]
2016-05-20 13:25   ` Joel Brobecker
2016-05-25 15:22     ` Pedro Alves
2016-05-25 17:45       ` Pedro Alves
2016-05-27 14:05         ` Joel Brobecker

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=395c33b0-7071-ed80-915a-dd8dbefe2786@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).