public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "keiths at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/23773] gdb crashed when I tried get backtrace
Date: Fri, 05 Jan 2024 19:50:41 +0000 [thread overview]
Message-ID: <bug-23773-4717-wshwjXlTOT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23773-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23773
Keith Seitz <keiths at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |keiths at redhat dot com
Resolution|--- |FIXED
Assignee|unassigned at sourceware dot org |keiths at redhat dot com
--- Comment #6 from Keith Seitz <keiths at redhat dot com> ---
(In reply to Hannes Domani from comment #5)
> (In reply to Sourceware Commits from comment #4)
> > The master branch has been updated by Keith Seitz <kseitz@sourceware.org>:
> >
> > https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;
> > h=c24bdb023c8e1fa969d6eb945059fa8ed0d490c7
> >
> > commit c24bdb023c8e1fa969d6eb945059fa8ed0d490c7
> > Author: Keith Seitz <keiths@redhat.com>
> > Date: Wed Jan 16 11:38:06 2019 -0800
> >
> > Introduce dwarf2_cu::get_builder
>
> Can this be closed?
Certainly seems like this was fixed a long time ago. Thank you for bringing
this to my attention!
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2024-01-05 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-23773-4717@http.sourceware.org/bugzilla/>
2024-01-04 22:24 ` ssbssa at sourceware dot org
2024-01-05 19:50 ` keiths at redhat dot com [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=bug-23773-4717-wshwjXlTOT@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).