This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug backtrace/15584] backtrace_command_1 does some unwinding too early
- From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 27 Mar 2018 04:06:34 +0000
- Subject: [Bug backtrace/15584] backtrace_command_1 does some unwinding too early
- Auto-submitted: auto-generated
- References: <bug-15584-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15584
--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=fb7eb8b5826f059e2b7a18e42ff9c20972e626bc
commit fb7eb8b5826f059e2b7a18e42ff9c20972e626bc
Author: Tom Tromey <tom@tromey.com>
Date: Mon Apr 24 21:03:22 2017 -0600
Move some code later in backtrace_command_1
PR backtrace/15584 notes that some code in backtrace_command_1 is not
useful when frame filters are in use. This patch moves this code into
the no-frame-filters "if". This also removes the unused local
"trailing_level", which I noticed while moving the code around.
gdb/ChangeLog
2018-03-26 Tom Tromey <tom@tromey.com>
PR backtrace/15584:
* stack.c (backtrace_command_1): Move some code into no-filters
"if".
--
You are receiving this mail because:
You are on the CC list for the bug.