From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 211033861027; Sat, 8 Aug 2020 12:43:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 211033861027 From: "trass3r at gmail dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: trass3r at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Aug 2020 12:43:19 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D26355 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 t= he 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=