From: Simon Marchi <simark@simark.ca>
To: Alexandra Petlanova Hajkova <ahajkova@redhat.com>,
Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] gdb: give sentinel for user frames distinct IDs, register sentinel frames to the frame cache
Date: Wed, 8 Feb 2023 16:37:35 -0500 [thread overview]
Message-ID: <439f134d-4648-b8bc-e55a-223c85b26402@simark.ca> (raw)
In-Reply-To: <CAJVr-EOvFGgVbeEM3kK0fuiLxmPYYMNYRF04iyDS4onxX2Q7-A@mail.gmail.com>
>
> I can see the patch set fixes gdb.base/frame-view.exp on aarch64, I've seen
> this failure before the patch which does not occur after applying it.
> frame
> #0 baz (z1=hahaha, ../../binutils-gdb/gdb/value.c:4056: internal-error: v
> alue_fetch_lazy_register: Assertion `next_frame != NULL' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> ----- Backtrace -----
> FAIL: gdb.base/frame-view.exp: with_pretty_printer=true: frame (GDB
> internal error)
> Resyncing due to internal error.
> 0x5a6aaf gdb_internal_backtrace_1
> ../../binutils-gdb/gdb/bt-utils.c:122
Thanks for the feedback, will add your Tested-By:
Tested-By: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
Simon
next prev parent reply other threads:[~2023-02-08 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 20:02 [PATCH 0/2] Fix gdb.base/frame-view.exp on AArch64 Simon Marchi
2023-01-30 20:02 ` [PATCH 1/2] gdb: call frame unwinders' dealloc_cache methods through destroying the frame cache Simon Marchi
2023-02-09 7:40 ` Tom de Vries
2023-02-09 12:42 ` Tom de Vries
2023-02-09 19:53 ` Simon Marchi
2023-01-30 20:02 ` [PATCH 2/2] gdb: give sentinel for user frames distinct IDs, register sentinel frames to " Simon Marchi
2023-02-07 17:02 ` Alexandra Petlanova Hajkova
2023-02-08 21:37 ` Simon Marchi [this message]
2023-02-08 17:05 ` Luis Machado
2023-02-08 21:38 ` Simon Marchi
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=439f134d-4648-b8bc-e55a-223c85b26402@simark.ca \
--to=simark@simark.ca \
--cc=ahajkova@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.com \
/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).