Mirror of the gdb-patches mailing list
 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.10 release 2015-08-21 status update
Date: Fri, 21 Aug 2015 12:41:00 -0000	[thread overview]
Message-ID: <55D71C68.6040600@redhat.com> (raw)
In-Reply-To: <20150821122639.GE30455@adacore.com>

On 08/21/2015 01:26 PM, Joel Brobecker wrote:
> Hello everyone,
> 
> I think we are definitely getting closer to release time!
> 
> The one question that might still be open is whether there is still
> work to be done regarding the "target:" default sysroot.
> 
> As far as I know, there has been some awesome work between Pedro and
> Gary to significantly reduce the time it takes to perform the file
> transfers.
> 
> There was also the question of being able to interrupt an on-going
> file tranfer, and I saw some promising patches, although Sandra reported
> that the quick-and-dirty proof-of-concept left GDB in an inconsistent
> state after interruption...

I'm having quite an interrupted day, but I'm trying to clean up
the hacky patch a bit.  Even if GDB ends up showing a couple
errors after disconnecting, like:

 You can't do that when your target is `exec'
 No registers.
 (gdb)

I think it's way better than getting stuck.  It's an escape hatch
for emergencies -- some bruising expected.  :-)  We can always clean
that up after the release, IMO.  I think those sort of errors can happen
if the connection drops unexpectedly at the wrong time, even
without the patch, for instance.

> 
> There was also a proposal to revert the default sysroot value back
> to "", with some added logic to make the "target:" implicit in some
> situations; but, as far as I know, this has been abandoned (and
> looking back, I would agree).
> 

I agree too, especially given we've fixed the major slowness
culprit.

> So, what do we still need to do before we can release?
> 
>   - Finish the work on being able to interrupt the file transfer?
> 
>   - There were some discussions about displaying a warning,
>     and I don't see anything in the current sources; are we still
>     thinking about that?

Yes, I think so.  Also Gary's QUIT patch should probably go in
as well, I think.

Thanks,
Pedro Alves


  reply	other threads:[~2015-08-21 12:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 12:26 Joel Brobecker
2015-08-21 12:41 ` Pedro Alves [this message]
2015-08-21 13:22   ` 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=55D71C68.6040600@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