Tom Tromey 918229560c off-by-one fix for py-linetable.c ...

While digging into a different memory corruption error, I happened to
notice one coming from the linetable code.  In a couple of spots, the
wrong termination condition was used in a loop, leading gdb to read
one element past the end of the linetable.

Built and regtested on x86-64 Fedora 18.  Also verified using
valgrind.  I'm checking this in.

2013-11-14  Tom Tromey  <tromey@redhat.com>

	* python/py-linetable.c (ltpy_has_line)
	(ltpy_get_all_source_lines): Fix loop termination condition.

2013-11-14 11:09:14 -07:00

..

lib/gdb

…

py-arch.c

…

py-auto-load.c

…

py-block.c

…

py-bpevent.c

…

py-breakpoint.c

…

py-cmd.c

…

py-continueevent.c

…

py-event.c

…

py-event.h

…

py-events.h

…

py-evtregistry.c

…

py-evts.c

…

py-exitedevent.c

…

py-finishbreakpoint.c

…

py-frame.c

…

py-framefilter.c

…

py-function.c

…

py-gdb-readline.c

…

py-inferior.c

…

py-infthread.c

…

py-lazy-string.c

…

py-linetable.c

off-by-one fix for py-linetable.c

2013-11-14 11:09:14 -07:00

py-newobjfileevent.c

…

py-objfile.c

…

py-param.c

…

py-prettyprint.c

…

py-progspace.c

…

py-signalevent.c

…

py-stopevent.c

…

py-stopevent.h

…

py-symbol.c

…

py-symtab.c

2013-11-11 Phil Muldoon <pmuldoon@redhat.com>

2013-11-11 19:49:45 +00:00

py-threadevent.c

…

py-type.c

…

py-utils.c

…

py-value.c

…

python-config.py

…

python-internal.h

2013-11-11 Phil Muldoon <pmuldoon@redhat.com>

2013-11-11 19:49:45 +00:00

python.c

2013-11-11 Phil Muldoon <pmuldoon@redhat.com>

2013-11-11 19:49:45 +00:00

python.h

…