public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "pmuldoon at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/16486] differences between "bt" and "bt no-filters" Date: Fri, 21 Feb 2014 12:55:00 -0000 [thread overview] Message-ID: <bug-16486-4717-zKSpnqrg2E@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16486-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16486 Phil Muldoon <pmuldoon at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pmuldoon at redhat dot com --- Comment #1 from Phil Muldoon <pmuldoon at redhat dot com> --- I've added the missing wrap hints in the same places as the "no-filter" option. I will submit that soon. However, I also noticed that for the first frame, the "no-filter" option does not print an address, but the frame filtered version does. I looked into this, and if the sal.pc == current_frame.pc then the address is not printed. (This is the line in GDB) Breakpoint 2, frame_show_address (frame=0x101ad50, sal=...) at ../../binutils-gdb/gdb/stack.c:146 146 return get_frame_pc (frame) != sal.pc; I thought about fixing this, but I think it is somewhat of an arbitrary decision for GDB to make over the frame filters. After all, each frame filter can either choose to show whatever address on whatever line it chooses. So I decided not to fix that. What do you think? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-02-21 12:55 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-22 6:56 [Bug python/16486] New: " tromey at redhat dot com 2014-02-21 12:55 ` pmuldoon at redhat dot com [this message] 2014-02-21 13:44 ` [Bug python/16486] " pmuldoon at redhat dot com 2014-02-21 15:42 ` tromey at redhat dot com 2014-02-26 9:01 ` pmuldoon at redhat 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-16486-4717-zKSpnqrg2E@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).