Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 18.1 release update -- 2026-09-01
Date: Mon, 07 Sep 2026 14:04:09 +0100	[thread overview]
Message-ID: <87qzj5qkl2.fsf@redhat.com> (raw)
In-Reply-To: <yddo6e9fi8a.fsf@CeBiTec.Uni-Bielefeld.DE>

Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:

> Hi Andrew,
>
>> Still Open Since Previous Update:
>> ---------------------------------
>>
>>  * dap/34548 - gdb.dap/pause.exp hangs on Solaris
>>    https://sourceware.org/bugzilla/show_bug.cgi?id=34548
>>
>>    A V2 patch was posted here:
>>
>>    https://inbox.sourceware.org/gdb-patches/ydd4iged3z5.fsf_-_@CeBiTec.Uni-Bielefeld.DE
>
> the patch (or rather the minor revision at
>
>      https://sourceware.org/pipermail/gdb-patches/2026-September/230000.html
>
> ) has now been committed to trunk.
>
>> Added Since the Last Update:
>> ----------------------------
>
> There's also
>
>   * corefiles/34555
>     https://sourceware.org/bugzilla/show_bug.cgi?id=34555
>
>     A patch has been posted, but not reviewed yet:
>
>     https://sourceware.org/pipermail/gdb-patches/2026-August/229698.html

I happy to track this bug for GDB 18, and I'll try to review this patch
next.  But... if I understand this bug report correctly, this is a long
standing bug in GDB, not a regression introduced in the last couple of
releases.  As such I'd prefer that we didn't hold the release for this
fix (which I will review next, so might be fixed anyway).

I'd really like to avoid holding the release for:

  + new features,
  + fixes for things that have never worked, or
  + fixes for things that have been broken for 2+ releases.

I'm about to send out another 'release update' and I plan to list this
bug under "nice to have".  Then I'll go and review the fix, so hopefully
we'll land this anyway.

I know that might not be the answer you were hoping for, but I will make
reviewing that patch a priority.

Thanks,
Andrew


      reply	other threads:[~2026-09-07 13:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 14:39 Andrew Burgess
2026-09-01 18:04 ` Tom Tromey
2026-09-01 19:37   ` Andrew Burgess
2026-09-03  6:31 ` Joos, Christina
2026-09-03  8:00   ` Andrew Burgess
2026-09-07 10:50 ` Rainer Orth
2026-09-07 13:04   ` Andrew Burgess [this message]

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=87qzj5qkl2.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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