public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Jose E.Marchesi <jemarch@sourceware.org> To: bfd-cvs@sourceware.org, gdb-cvs@sourceware.org Subject: [binutils-gdb] libctf: fix tabdamage Date: Thu, 03 Oct 2019 16:34:00 -0000 [thread overview] Message-ID: <20191003163415.121409.qmail@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=fa56cdcd2427e701328ae1e20b0ca7916d580a14 commit fa56cdcd2427e701328ae1e20b0ca7916d580a14 Author: Nick Alcock <nick.alcock@oracle.com> Date: Thu Sep 26 15:26:48 2019 +0100 libctf: fix tabdamage A little tabdamage predating the linker patch series has crept in. New in v5. libctf/ * ctf-open.c (ctf_bufopen_internal): Fix tabdamage. * ctf-types.c (ctf_type_lname): Likewise. Diff: --- libctf/ChangeLog | 5 +++++ libctf/ctf-open.c | 4 ++-- libctf/ctf-types.c | 2 +- 3 files changed, 8 insertions(+), 3 deletions(-) diff --git a/libctf/ChangeLog b/libctf/ChangeLog index 982c335..27652b8 100644 --- a/libctf/ChangeLog +++ b/libctf/ChangeLog @@ -1,3 +1,8 @@ +2019-09-30 Nick Alcock <nick.alcock@oracle.com> + + * ctf-open.c (ctf_bufopen_internal): Fix tabdamage. + * ctf-types.c (ctf_type_lname): Likewise. + 2019-09-23 Nick Alcock <nick.alcock@oracle.com> * ctf-open.c (ctf_import): Do not leak a ctf_file_t ref on every diff --git a/libctf/ctf-open.c b/libctf/ctf-open.c index aedf390..7fb289a 100644 --- a/libctf/ctf-open.c +++ b/libctf/ctf-open.c @@ -1542,8 +1542,8 @@ ctf_bufopen_internal (const ctf_sect_t *ctfsect, const ctf_sect_t *symsect, (err = flip_ctf (hp, fp->ctf_buf)) != 0) { /* We can be certain that flip_ctf() will have endian-flipped everything - other than the types table when we return. In particular the header - is fine, so set it, to allow freeing to use the usual code path. */ + other than the types table when we return. In particular the header + is fine, so set it, to allow freeing to use the usual code path. */ ctf_set_base (fp, hp, fp->ctf_base); goto bad; diff --git a/libctf/ctf-types.c b/libctf/ctf-types.c index 27cbfb9..b0139e8 100644 --- a/libctf/ctf-types.c +++ b/libctf/ctf-types.c @@ -441,7 +441,7 @@ ctf_type_lname (ctf_file_t *fp, ctf_id_t type, char *buf, size_t len) size_t slen; if (str == NULL) - return CTF_ERR; /* errno is set for us */ + return CTF_ERR; /* errno is set for us. */ slen = strlen (str); snprintf (buf, len, "%s", str);
reply other threads:[~2019-10-03 16:34 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=20191003163415.121409.qmail@sourceware.org \ --to=jemarch@sourceware.org \ --cc=bfd-cvs@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).