public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug fortran/26155] p cos(alat(j)) command make gdb Aborted (core dumped)
Date: Thu, 25 Feb 2021 12:00:32 +0000 [thread overview]
Message-ID: <bug-26155-4717-2QuefuHhrK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26155-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26155
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Andrew Burgess from comment #4)
> Tom,
>
> Sorry I didn't spot you'd commented on this bug. I've had this patch sat on
> the mailing list since last year, but only got around to addressing the
> feedback and merging it recently.
>
Np. Ah, I see, that's
https://sourceware.org/pipermail/gdb-patches/2020-July/170493.html .
Yeah, that's on of the reasons why I always try to note at least the first
submitted patch for a PR in the PR.
> This issue should be resolved now. Feel free to reopen the bug if you
> continue to see this problem.
Ack, thanks for fixing this :)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-25 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 1:26 [Bug fortran/26155] New: " yansendao at huawei dot com
2021-02-03 12:40 ` [Bug fortran/26155] " vries at gcc dot gnu.org
2021-02-03 12:49 ` vries at gcc dot gnu.org
2021-02-25 10:33 ` cvs-commit at gcc dot gnu.org
2021-02-25 10:43 ` andrew.burgess at embecosm dot com
2021-02-25 11:58 ` vries at gcc dot gnu.org
2021-02-25 12:00 ` vries at gcc dot gnu.org [this message]
2021-02-25 14:45 ` tromey at sourceware dot org
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=bug-26155-4717-2QuefuHhrK@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).