Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: GDB Administrator <gdbadmin@sourceware.org>
To: gdb-patches@sourceware.org
Subject: New ARI warning Tue Aug  2 02:08:00 UTC 2016 in gdb-7.12-branch
Date: Tue, 02 Aug 2016 02:08:00 -0000	[thread overview]
Message-ID: <20160802020800.GA28719@sourceware.org> (raw)

259a260
> gdb/inflow.c:401: regression: ATTRIBUTE_UNUSED: Do not use ATTRIBUTE_UNUSED, do not bother (GDB is compiled with -Werror and, consequently, is not able to tolerate false warnings.  Since -Wunused-param produces such warnings, neither that warning flag nor ATTRIBUTE_UNUSED are used by GDB
gdb/inflow.c:401:      int result ATTRIBUTE_UNUSED;
290a292
> gdb/linux-nat.c:1456: regression: strerror: Do not use strerror(), instead use safe_strerror()
gdb/linux-nat.c:1456:		       lwpid, strerror (errno));
335d336
< gdb/mips-tdep.c:6991: deprecated: deprecated mips_set_processor_regs_hack: Do not use deprecated mips_set_processor_regs_hack, see declaration for details
gdb/mips-tdep.c:6991:deprecated_mips_set_processor_regs_hack (void)
338d338
< gdb/mips-tdep.h:148: deprecated: deprecated mips_set_processor_regs_hack: Do not use deprecated mips_set_processor_regs_hack, see declaration for details
gdb/mips-tdep.h:148:extern void deprecated_mips_set_processor_regs_hack (void);
479,503d478
< gdb/remote-mips.c:1254: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:1254:	sprintf (buff, ', cmd,
< gdb/remote-mips.c:1257: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:1257:	sprintf (buff, ', cmd,
< gdb/remote-mips.c:1458: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:1458:		sprintf (tbuff, ');
< gdb/remote-mips.c:1612: code: if assignment: An IF statement's expression contains an assignment (the GNU coding standard discourages this)
gdb/remote-mips.c:1612:	    if ((local_name = strchr (remote_name, '.')) != NULL)
< gdb/remote-mips.c:1643: deprecated: deprecated mips_set_processor_regs_hack: Do not use deprecated mips_set_processor_regs_hack, see declaration for details
gdb/remote-mips.c:1643:  deprecated_mips_set_processor_regs_hack ();
< gdb/remote-mips.c:2614: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:2614:	  sprintf (buf, ', i);
< gdb/remote-mips.c:2656: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:2656:	      sprintf (buf, ', phex_nz (addr, addr_size));
< gdb/remote-mips.c:2662: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:2662:	      sprintf (buf, ',
< gdb/remote-mips.c:2729: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:2729:	  sprintf (buf, ', phex_nz (addr, addr_size),
< gdb/remote-mips.c:2735: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:2735:	  sprintf (buf, ', phex_nz (addr, addr_size));
< gdb/remote-mips.c:2859: deprecated: deprecated ui_load_progress_hook: Do not use deprecated ui_load_progress_hook, see declaration for details
gdb/remote-mips.c:2859:	      if (deprecated_ui_load_progress_hook)
< gdb/remote-mips.c:2860: deprecated: deprecated ui_load_progress_hook: Do not use deprecated ui_load_progress_hook, see declaration for details
gdb/remote-mips.c:2860:		deprecated_ui_load_progress_hook (s->name, i);
< gdb/remote-mips.c:3056: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:3056:  sprintf (*buff, ');
< gdb/remote-mips.c:3083: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:3083:  sprintf (*buff, ');
< gdb/remote-mips.c:3086: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:3086:  sprintf (*buff, ');
< gdb/remote-mips.c:3152: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:3152:	  sprintf (p, ');
< gdb/remote-mips.c:3227: code: if assignment: An IF statement's expression contains an assignment (the GNU coding standard discourages this)
gdb/remote-mips.c:3227:      if ((tftp_file = fopen (tftp_localname, ')) == NULL)
< gdb/remote-mips.c:3274: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:3274:  sprintf (hexnumber, ', final);
< gdb/remote-mips.c:3289: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:3289:  sprintf (hexnumber, ', bintotal);
< gdb/remote-mips.c:3433: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:3433:  sprintf (buffer, ');
< gdb/remote-mips.c:3450: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:3450:	sprintf (buffer, ');
< gdb/remote-mips.c:3495: deprecated: deprecated ui_load_progress_hook: Do not use deprecated ui_load_progress_hook, see declaration for details
gdb/remote-mips.c:3495:			if (deprecated_ui_load_progress_hook)
< gdb/remote-mips.c:3496: deprecated: deprecated ui_load_progress_hook: Do not use deprecated ui_load_progress_hook, see declaration for details
gdb/remote-mips.c:3496:			  deprecated_ui_load_progress_hook (s->name, i);
< gdb/remote-mips.c:3530: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:3530:  sprintf (buffer, ');	 
< gdb/remote-mips.c:3616: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
gdb/remote-mips.c:3616:  sprintf (buf, ', args);
567a543
> gdb/rust-lang.c:1060: code: OP eol: Do not use &&, or || at the end of a line
gdb/rust-lang.c:1060:      = (TYPE_FIELD_BITPOS (result, i - 1) / TARGET_CHAR_BIT +
740a717
> gdb/windows-nat.c:840: code: OP eol: Do not use &&, or || at the end of a line
gdb/windows-nat.c:840:  if ((errno == ERANGE) || (event_id == 0) || (event_id > UINTPTR_MAX) ||


             reply	other threads:[~2016-08-02  2:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02  2:08 GDB Administrator [this message]
2016-08-02 13:30 ` Joel Brobecker

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=20160802020800.GA28719@sourceware.org \
    --to=gdbadmin@sourceware.org \
    --cc=gdb-patches@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: link
Be 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