public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 11 branching update (2021-06-13)
Date: Sun, 13 Jun 2021 16:57:01 +0200	[thread overview]
Message-ID: <50991ca967800d584967126f0b6e2a49970b6e30.camel@skynet.be> (raw)
In-Reply-To: <20210613143156.GA1615771@adacore.com>

The below patch completes/fixes the user manual and gdb --help.

Eli has has reviewed the user manual changes, I have fixed the 2 comments he gave.
The --help changes are quite trivial (only fixes in the help text and a small
change so that -w --windows starts the TUI if configured).

https://sourceware.org/pipermail/gdb-patches/2021-June/179834.html


It is for sure not critical, but might be suitable for GDB 11

Thanks
Philippe


On Sun, 2021-06-13 at 07:31 -0700, Joel Brobecker wrote:
> Hey Team,
> 
> Here is another udpate of where we are. We've actually made more
> progress than one might think by just looking at the number of items
> alone, so last week was a good week. Keep it up :).
> 
> 
> Fixed Since the Previous Update:
> --------------------------------
> 
>   * [Simon] <PR gdb/27899>
>     [GNU/Linux, sparc64] GDB crashes when debugging multithreaded programs
>     https://sourceware.org/bugzilla/show_bug.cgi?id=27899
> 
> 
> Added Since the Last Update:
> ----------------------------
> 
>   < none :) >
> 
> Other Ongoing Items:
> --------------------
> 
>   * [TomDV] <PR symtab/26327>
>     GDB hangs in get_builder() due to recursive ancestor pointers
>     https://sourceware.org/bugzilla/show_bug.cgi?id=26327
> 
>     2021-06-09: Patch submitted:
>     https://sourceware.org/pipermail/gdb-patches/2021-June/179750.html
> 
>   * [Simon/Kevin] <PR gdb/27526>
>     Attaching to threaded process on glibc 2.33: libthread_db fails to initialize with "generic error"
>     https://sourceware.org/bugzilla/show_bug.cgi?id=27526
> 
>     2021-06-10: Looks like we're getting close. New patch series from
>     Kevin, with positive reviews (modulo minor comments or questions):
>     https://sourceware.org/pipermail/gdb-patches/2021-June/179786.html
> 
>   * [RainerO] <PR binutils/27666>
>     ar doesn't create indices on Solaris/sparcv9
>     https://sourceware.org/bugzilla/show_bug.cgi?id=27666
> 
>     Causes large number of tests to fail in gdb's testsuite.
> 
>     2021-06-09: Binutils patch pushed to master should normally
>     make the issue go away (waiting for confirmation):
>     https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f75bcf7e574c511f0ea742e05e5ae6e19bf29a92
> 
>   * [LuisM] <PR corefiles/27909>
>     AArch64 MTE fixes and corefile support
>     https://sourceware.org/bugzilla/show_bug.cgi?id=27909
> 
>   * [Bernd/PedroA/TomT] TUI issues from mouse-support patch
>     https://sourceware.org/pipermail/gdb-patches/2021-June/179541.html
> 
>     Under discussion, but looks like there is good progress.
>     It's a bit difficult for me to follow the discussions because
>     I don't know TUI -- would you let me know when you think
>     all blocking issues have been resolved?
> 
> Not Critical, but Requested:
> ----------------------------
> 
>   * [BerndE] Improve debugging of optimized code
>     https://sourceware.org/pipermail/gdb-patches/2021-January/175617.html
> 
>     (2021-05-31) v2 posted at:
>       [0/4] https://sourceware.org/pipermail/gdb-patches/2021-May/179367.html
>       [1/4] https://sourceware.org/pipermail/gdb-patches/2021-May/179368.html
>       [2/4] https://sourceware.org/pipermail/gdb-patches/2021-May/179370.html
>       [3/4] https://sourceware.org/pipermail/gdb-patches/2021-May/179369.html
> 
>   * [Sergey with Simon as reviewer] <PR tdep/26633>
>     Add Z80 CPU support
>     https://sourceware.org/bugzilla/show_bug.cgi?id=26633
> 
>     Patch submitted at:
>     https://sourceware.org/pipermail/gdb-patches/2020-September/172083.html
> 
>     (May 24th) High-level pre-review done at:
>     https://sourceware.org/pipermail/gdb-patches/2021-May/179191.html
> 
>     No movement since then. Not blocking for branching since it would
>     be safe to backport after branching. Not blocking for release either.
> 
>   * [Simon] <PR gdb/26868>
>     Follow-up on x86-64 stub submission
>     https://sourceware.org/bugzilla/show_bug.cgi?id=26868
> 
>     This is the submission in question:
>     https://sourceware.org/pipermail/gdb-patches/2020-November/173182.html
> 
>     For me, although I am not a lawyer, I don't think we can accept
>     the contribution without the author signing a copyright assignment
>     form.
> 
> Thank you!


  reply	other threads:[~2021-06-13 14:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-13 14:31 Joel Brobecker
2021-06-13 14:57 ` Philippe Waroquiers [this message]
2021-06-13 15:30   ` Joel Brobecker
2021-06-14  7:44 ` Kevin Buettner
2021-06-17  7:36 ` Rainer Orth
2021-06-17 11:16 ` Pedro Alves
2021-06-17 15:01   ` Hannes Domani
2021-07-02 15:34   ` Pedro Alves

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=50991ca967800d584967126f0b6e2a49970b6e30.camel@skynet.be \
    --to=philippe.waroquiers@skynet.be \
    --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).