public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/26364] [aarch64] gdb/frame.c:593: internal-error: frame_id get_frame_id(frame_info*): Assertion `stashed' failed.
Date: Wed, 12 Aug 2020 13:46:27 +0000 [thread overview]
Message-ID: <bug-26364-4717-Daa86dBhEl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26364-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26364
--- Comment #9 from Simon Marchi <simark at simark dot ca> ---
(In reply to Tom de Vries from comment #8)
> (In reply to Simon Marchi from comment #5)
> > I'm chasing a problem that may or may not be related (I'll probably post a
> > patch soon). Could you post a backtrace of GDB? I could see if the
> > backtrace looks familiar.
>
> It would be great if gdb emitted a backtrace upon abort, that could really
> help with hard-to-reproduce problems ( FTR, mentioned this possibility here:
> https://sourceware.org/pipermail/gdb/2020-July/048788.html ).
Agreed. How easy is it to do, are there libraries that can help with that?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-08-12 13:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 14:37 [Bug tdep/26364] New: " vries at gcc dot gnu.org
2020-08-10 14:38 ` [Bug tdep/26364] " vries at gcc dot gnu.org
2020-08-11 13:30 ` luis.machado at linaro dot org
2020-08-11 14:17 ` vries at gcc dot gnu.org
2020-08-11 14:17 ` vries at gcc dot gnu.org
2020-08-11 19:20 ` luis.machado at linaro dot org
2020-08-11 19:23 ` simark at simark dot ca
2020-08-12 12:59 ` vries at gcc dot gnu.org
2020-08-12 13:25 ` vries at gcc dot gnu.org
2020-08-12 13:38 ` vries at gcc dot gnu.org
2020-08-12 13:46 ` simark at simark dot ca [this message]
2020-08-12 13:51 ` vries at gcc dot gnu.org
2020-08-12 14:34 ` vries at gcc dot gnu.org
2020-08-16 11:36 ` vries at gcc dot gnu.org
2020-08-18 16:54 ` vries at gcc dot gnu.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-26364-4717-Daa86dBhEl@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).