Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jonah Graham <jonah@kichwacoders.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: bernd.edlinger@hotmail.de, gdb-patches@sourceware.org
Subject: Re: GDB 11.1 release prep update (2021-07-11)
Date: Sun, 11 Jul 2021 15:43:07 -0400	[thread overview]
Message-ID: <CAPmGMvhbvTNCDLmRuVdeVOT6DXwdN4J_Fc25uiJd8RVK6ih76g@mail.gmail.com> (raw)
In-Reply-To: <CAPmGMvgeKwurOnu=82uU9Vqtjho_R-ORcwgAw=CQGyK6+HGDsg@mail.gmail.com>

On Sun, 11 Jul 2021 at 13:04, Jonah Graham <jonah@kichwacoders.com> wrote:

>
> On Sun, 11 Jul 2021 at 10:44, Joel Brobecker <brobecker@adacore.com>
> wrote:
>
>> Hi everyone,
>>
>> Here is a quick status of where we are today, in terms of the GDB 11.1
>> release.
>>
>> We branched last week (hurray!), and so far, we haven't received news
>> of any major issues. So we're left with the issues listed below,
>> with some being absolutely blocking, and others being a bit less so.
>>
>> For those who have the time and expertise, it would be awesome if
>> we could prioritize those issues.
>>
>>
> Hi Joel,
>
> I have an issue and will raise a bug (regression compared to 10.2) as soon
> as possible with a reproducer. In the meantime, the summary looks like
> doing an MI "-exec-interrupt --thread-group i1" causes an assertion failure:
>
> ~"/scratch/gdb/binutils-gdb/gdb/target.c:3768: internal-error: void
> target_stop(ptid_t): Assertion `!proc_target->commit_resumed_state'
> failed.\nA problem internal to GDB has been detected,\nfurther debugging
> may prove unreliable."
>
> I hit this when using Eclipse CDT on x86_64 linux.
>
> If someone recognizes this as a duplicate, please let me know.
>
> Jonah
>

Hi Joel,

The above issue is a regression, I have raised
https://sourceware.org/bugzilla/show_bug.cgi?id=28077 for it.

There is another regression, also affecting Eclipse CDT, when using
"-break-condition N" to remove a condition. I have raised
https://sourceware.org/bugzilla/show_bug.cgi?id=28076 for it.

Thanks
Jonah




>
>

  reply	other threads:[~2021-07-11 19:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-11 14:43 Joel Brobecker
2021-07-11 17:04 ` Jonah Graham
2021-07-11 19:43   ` Jonah Graham [this message]
2021-07-12  2:21     ` Jonah Graham
2021-07-12  2:23       ` Jonah Graham
2021-07-12 15:37         ` Jonah Graham
2021-07-12 22:27           ` Jonah Graham
2021-07-13 14:37             ` Joel Brobecker
2021-07-17 14:37 ` Simon Marchi via Gdb-patches

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=CAPmGMvhbvTNCDLmRuVdeVOT6DXwdN4J_Fc25uiJd8RVK6ih76g@mail.gmail.com \
    --to=jonah@kichwacoders.com \
    --cc=bernd.edlinger@hotmail.de \
    --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