public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "plasmahh at gmx dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/30614] New: Consider allowing to provide alternative stack for backtraces
Date: Tue, 04 Jul 2023 08:56:32 +0000	[thread overview]
Message-ID: <bug-30614-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30614

            Bug ID: 30614
           Summary: Consider allowing to provide alternative stack for
                    backtraces
           Product: gdb
           Version: unknown
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: backtrace
          Assignee: unassigned at sourceware dot org
          Reporter: plasmahh at gmx dot net
  Target Milestone: ---

gdb allows to view a single frame living on an alternative stack

> help frame view
View a stack frame that might be outside the current backtrace.

Usage: frame view STACK-ADDRESS
       frame view STACK-ADDRESS PC-ADDRESS



Especially in (embedded) environments where gdb is not aware of e.g. user
threads it would be helpful if the backtrace command could accept the same
optional parameters to start unwinding at that alternative stack.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-07-04  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04  8:56 plasmahh at gmx dot net [this message]
2023-07-04 15:36 ` [Bug backtrace/30614] " tromey at sourceware dot org
2023-07-05 14:48 ` 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-30614-4717@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).