From: Joel Brobecker <brobecker@adacore.com>
To: Magne Hov via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] gdb: fix eval.c assert during inferior exit event
Date: Mon, 24 May 2021 12:23:52 -0700 [thread overview]
Message-ID: <20210524192352.GA755333@adacore.com> (raw)
In-Reply-To: <20210510172121.2123009-1-mhov@undo.io>
Hello Magne,
> 2021-05-10 Magne Hov <mhov@undo.io>
>
> * eval.c (expression::evaluate): Check inferior_ptid.
>
> gdb/testsuite/ChangeLog:
>
> 2021-05-10 Magne Hov <mhov@undo.io>
>
> * gdb.python/py-events.exp: Extend inferior exit tests.
> * gdb.python/py-events.py: Print inferior exit PID.
A quick request when the copyright assignment process is complete;
since Simon created a PR in bugzilla to track this issue, would
you mind adding...
PR python/27841
... at the start of each ChangeLog entry above, when you push the
commit? This way, you commit gets automatically filed into that PR
in bugzilla as well.
If you look at the current ChangeLog files, you'll find lots of
examples.
Thank you!
--
Joel
next prev parent reply other threads:[~2021-05-24 19:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 15:56 [RFC PATCH] " Magne Hov
2021-05-06 1:59 ` Simon Marchi
2021-05-10 16:57 ` Magne Hov
2021-05-10 17:33 ` Simon Marchi
2021-05-10 17:21 ` [PATCH v2] " Magne Hov
2021-05-10 17:44 ` Simon Marchi
2021-05-14 16:24 ` Magne Hov
2021-05-11 7:16 ` Aktemur, Tankut Baris
2021-05-14 16:22 ` Magne Hov
2021-05-24 19:23 ` Joel Brobecker [this message]
2021-05-26 13:02 ` [PATCH v3] " Magne Hov
2021-05-29 2:25 ` Simon Marchi
2021-06-02 11:34 ` Magne Hov
2021-06-03 21:07 ` Magne Hov
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=20210524192352.GA755333@adacore.com \
--to=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).