public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Consolidate "Python API" sections in NEWS Date: Mon, 6 Jun 2022 19:10:01 +0000 (GMT) [thread overview] Message-ID: <20220606191001.4FA973834E79@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=691ade38bc45f4d4c89c0d6a3412bc160cf40a70 commit 691ade38bc45f4d4c89c0d6a3412bc160cf40a70 Author: Tom Tromey <tromey@adacore.com> Date: Mon Jun 6 13:07:37 2022 -0600 Consolidate "Python API" sections in NEWS I noticed that the gdb NEWS file had two "Python API" sections in "Changes since GDB 12". This patch consolidates the two. I chose to preserve the second one, first because it is longer, and second because I felt that user command changes should come before API changes. Diff: --- gdb/NEWS | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/gdb/NEWS b/gdb/NEWS index 960f90b4387..a85f59f56df 100644 --- a/gdb/NEWS +++ b/gdb/NEWS @@ -27,13 +27,6 @@ emit to indicate where a breakpoint should be placed to break in a function past its prologue. -* Python API - - ** GDB will now reformat the doc string for gdb.Command and - gdb.Parameter sub-classes to remove unnecessary leading - whitespace from each line before using the string as the help - output. - * New commands maintenance set ignore-prologue-end-flag on|off @@ -52,6 +45,11 @@ maintenance info line-table * Python API + ** GDB will now reformat the doc string for gdb.Command and + gdb.Parameter sub-classes to remove unnecessary leading + whitespace from each line before using the string as the help + output. + ** New function gdb.format_address(ADDRESS, PROGSPACE, ARCHITECTURE), that formats ADDRESS as 'address <symbol+offset>', where symbol is looked up in PROGSPACE, and ARCHITECTURE is used to format address.
reply other threads:[~2022-06-06 19:10 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220606191001.4FA973834E79@sourceware.org \ --to=tromey@sourceware.org \ --cc=gdb-cvs@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).