Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] bitpos expansion summary reloaded
Date: Sat, 29 Sep 2012 17:39:00 -0000	[thread overview]
Message-ID: <20120929173938.GA2987@host2.jankratochvil.net> (raw)
In-Reply-To: <20120927190053.1e7de264@spoyarek>

Hi Siddhesh,

I have reported without effect:
	But for example ada-valprint.c:700 is not reported in this file at all, why?

ada-valprint.c:700 is the last line of this extracted code:
  LONGEST offset;
  int offset_aligned;
  const gdb_byte *valaddr;
  const gdb_byte *ada_aligned_value_addr (struct type *type, const gdb_byte *valaddr);
  offset_aligned = offset + ada_aligned_value_addr (type, valaddr) - valaddr;

Reduced testcase:
int main (void) {
  const char *a = "", *b = "";
  int reported, missed;
  long longvar = 0;
  reported = longvar;
  missed = longvar + a - b;
  return reported + missed; }

splint -hints -linelen 999:
../../../t/t.c: (in function main)
../../../t/t.c:5:3: Assignment of long int to int: reported = longvar

splint -hints -linelen 999 -checks:
../../../t/t.c: (in function main)
../../../t/t.c:5:3: Assignment of long int to int: reported = longvar
../../../t/t.c:6:22: Pointer arithmetic involving possibly null pointer a: longvar + a

splint -hints -linelen 999 -strict:
../../../t/t.c: (in function main)
../../../t/t.c:5:3: Assignment of long int to int: reported = longvar
../../../t/t.c:6:12: Pointer arithmetic (long int, char *): longvar + a
../../../t/t.c:6:22: Pointer arithmetic involving possibly null pointer a: longvar + a
../../../t/t.c:6:12: Operands of - are non-numeric (char *): longvar + a - b

These warnings are in fact OK but the problematic assignment
of ptrdiff_t to int variable 'missed' is not reported at all.

We need to either fix splint or (more likely) use a different tool, there are
too many cases missed this way.


Regards,
Jan


  parent reply	other threads:[~2012-09-29 17:39 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27 13:33 Siddhesh Poyarekar
2012-09-28 11:20 ` Jan Kratochvil
2012-09-28 11:40   ` Siddhesh Poyarekar
2012-09-28 12:06     ` Jan Kratochvil
2012-09-28 12:19       ` Siddhesh Poyarekar
2012-09-29 17:39 ` Jan Kratochvil [this message]
2012-09-29 18:12   ` Jan Kratochvil
2012-09-30  6:52     ` Jan Kratochvil
2012-10-01  5:21       ` Siddhesh Poyarekar
2012-10-01  6:14         ` Jan Kratochvil
2012-10-03 13:12       ` Siddhesh Poyarekar
2012-10-03 18:38         ` Jan Kratochvil
2012-10-04  7:20           ` Siddhesh Poyarekar
2012-10-03 19:56         ` Jan Kratochvil
2012-10-04  7:13           ` Jan Kratochvil
2012-10-21  7:36             ` Siddhesh Poyarekar
2012-10-22 20:45               ` Tom Tromey
2012-10-23  1:34                 ` Jan Kratochvil
2012-10-23  1:58                   ` Jan Kratochvil
2012-10-23  2:29                     ` Siddhesh Poyarekar
2012-10-23  2:37                       ` Jan Kratochvil
2012-10-23  2:38                   ` Tom Tromey
2012-10-23 19:11               ` Jan Kratochvil
2012-10-24 18:33                 ` Tom Tromey
2012-10-24 18:55                   ` Jan Kratochvil
2012-10-24 20:18                     ` Tom Tromey
2012-10-25 15:54               ` Jan Kratochvil
2012-10-25 16:52                 ` Siddhesh Poyarekar
2012-11-06 20:01                   ` Jan Kratochvil
2012-11-07 13:48                     ` Jan Kratochvil
2012-11-13 19:46                       ` Tom Tromey
2012-11-13 19:55                         ` Jan Kratochvil
2012-11-01 15:24               ` Jan Kratochvil
2012-11-01 16:56                 ` Siddhesh Poyarekar

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=20120929173938.GA2987@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=siddhesh@redhat.com \
    /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