public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29865] The GDB dies during unwind the stack - question
Date: Wed, 07 Dec 2022 23:02:14 +0000 [thread overview]
Message-ID: <bug-29865-4717-KUbDxvnaNj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29865-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29865
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
Offhand I'm not sure what the deal is here.
Maybe "set backtrace limit" has to take this situation
into account and allow some leeway, or maybe it
should only work on "physical" (non-inline/tailcall)
frames -- dunno. (And, assuming that's what you did...)
However - what version of gdb are you using?
This assert doesn't seem to appear in git master.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-07 23:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 15:24 [Bug gdb/29865] New: " filip.bascarevic at siemens dot com
2022-12-07 23:02 ` tromey at sourceware dot org [this message]
2022-12-08 7:55 ` [Bug gdb/29865] " filip.bascarevic at siemens dot com
2022-12-21 18:42 ` tromey at sourceware dot org
2024-01-06 14:01 ` ssbssa at sourceware dot org
2024-01-06 20:16 ` ssbssa at sourceware dot org
2024-01-06 20:16 ` ssbssa at sourceware dot org
2024-01-29 14:34 ` cvs-commit at gcc dot gnu.org
2024-01-29 14:36 ` ssbssa 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-29865-4717-KUbDxvnaNj@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).