public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] new warnings to catch from gcc in portage
@ 2010-06-20  9:26 Mike Frysinger
  2010-07-19 21:22 ` Mike Frysinger
  0 siblings, 1 reply; 2+ messages in thread
From: Mike Frysinger @ 2010-06-20  9:26 UTC (permalink / raw
  To: gentoo-dev

[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]

the newer fortify/security work in gcc provides some nice checks which portage 
doesnt currently flag.  those are:
	": warning: array subscript is below array bounds$"
	": warning: array subscript is above array bounds$"
	": warning: attempt to free a non-heap object"
	": warning: .* called with .*bigger.* than .* destination buffer$"
	": warning: call to .* will always overflow destination buffer$"

this should catch the kind of checks where people check for pointer math 
overflow but dont realize that gcc optimizes it away:
	": warning: assuming pointer wraparound does not occur when comparing "

these tend to be typos in code:
	": warning: hex escape sequence out of range$"
	": warning: [^ ]*-hand operand of comma .*has no effect$"

these too are typos/thinkos involving NULL instead of a value of 0, or 
misordering of arguments:
	": warning: converting to non-pointer type .* from NULL"
	": warning: NULL used in arithmetic$"
	": warning: passing NULL to non-pointer argument"

these tend to be thinkos which result in incorrect behavior:
	": warning: the address of [^ ]* will always evaluate as"
	": warning: the address of [^ ]* will never be NULL"
think "char foo[1234]" and later doing "if (foo) ..."

i cant see this being valid:
	": warning: too few arguments for format"

or trying to return addresses to function locals:
	": warning: reference to local variable .* returned"
	": warning: returning reference to temporary"
	": warning: function returns address of local variable"
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [gentoo-dev] new warnings to catch from gcc in portage
  2010-06-20  9:26 [gentoo-dev] new warnings to catch from gcc in portage Mike Frysinger
@ 2010-07-19 21:22 ` Mike Frysinger
  0 siblings, 0 replies; 2+ messages in thread
From: Mike Frysinger @ 2010-07-19 21:22 UTC (permalink / raw
  To: gentoo-dev

[-- Attachment #1: Type: Text/Plain, Size: 81 bytes --]

no feed back, so pushed to latest portage.  guess we'll see what blows up.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-07-19 21:25 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-06-20  9:26 [gentoo-dev] new warnings to catch from gcc in portage Mike Frysinger
2010-07-19 21:22 ` Mike Frysinger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox