public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "trass3r at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/26355] New: get list of candidate functions to step into Date: Sat, 08 Aug 2020 12:43:18 +0000 [thread overview] Message-ID: <bug-26355-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26355 Bug ID: 26355 Summary: get list of candidate functions to step into Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: trass3r at gmail dot com Target Milestone: --- Is there a way in gdb to get a list of functions you could step into when the current line of code is composed of several function calls like `foo(computeParam1(), computeParam2(), computeParam3())`? This is necessary to implement https://github.com/Microsoft/vscode-cpptools/issues/2488. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-08-08 12:43 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-08 12:43 trass3r at gmail dot com [this message] 2020-08-09 19:33 ` [Bug gdb/26355] " tromey at sourceware dot org 2020-08-24 17:50 ` trass3r at gmail dot com
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-26355-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: linkBe 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).