From: Mark Williams <mark@myosotissp.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix assertion fi->level
Date: Mon, 03 Feb 2020 03:05:00 -0000 [thread overview]
Message-ID: <CAN0QdPUw5nw8-ELYV5cWtqsr5z_Gwxb4bq61m9m4omWtofVAnQ@mail.gmail.com> (raw)
In-Reply-To: <CAN0QdPUhv1maL+0B2B1t0GabB8-aTQ=f+VAu8cVNHwA6GV2c-Q@mail.gmail.com>
Apparently I should ping the thread after 2 weeks with no response...
Note that python unwinders are completely unusable in gdb-8.1 and
later without this fix...
On Sun, Jan 19, 2020 at 9:20 AM Mark Williams <mark@myosotissp.com> wrote:
>
> Add a test case, and more detail to the commit message
next prev parent reply other threads:[~2020-02-03 3:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 23:04 Mark Williams
2020-01-19 17:27 ` Mark Williams
2020-02-03 3:05 ` Mark Williams [this message]
2020-02-07 21:04 ` Tom Tromey
2020-02-07 21:09 ` Mark Williams
2020-02-09 18:57 ` Mark Williams
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=CAN0QdPUw5nw8-ELYV5cWtqsr5z_Gwxb4bq61m9m4omWtofVAnQ@mail.gmail.com \
--to=mark@myosotissp.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