This is the mail archive of the gdb-cvs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

src/gdb ChangeLog value.c


CVSROOT:	/cvs/src
Module name:	src
Changes by:	palves@sourceware.org	2013-07-04 16:08:23

Modified files:
	gdb            : ChangeLog value.c 

Log message:
	value_bits_valid: Fix latent bug.
	
	Doing something else, I factored out the bits of the value_bits_valid
	function that actually handle the check_validity hook, and
	surprisingly found out that the result was misbehaving.  Turns out
	value_bits_valid has a latent bug.  If the value is not lval_computed,
	or doesn't have a check_validity hook, then we should assume the value
	is entirely valid, not invalid.  This is currently masked by the
	value->optimized_out check -- I ran the testsuite with a gdb_assert(0)
	inserted in place of that return being touched by the patch, and it
	never triggers.
	
	Tested on x86_64 Fedora 17.
	
	gdb/
	2013-07-04  Pedro Alves  <palves@redhat.com>
	
	* value.c (value_bits_valid): If the value is not lval_computed,
	or doesn't have a check_validity hook, assume the value is entirely
	valid.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/ChangeLog.diff?cvsroot=src&r1=1.15784&r2=1.15785
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/value.c.diff?cvsroot=src&r1=1.172&r2=1.173


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]