public inbox for src-cvs@sourceware.org help / color / mirror / Atom feed
From: tromey@sourceware.org To: src-cvs@sourceware.org Subject: gdb and binutils branch master updated. 918229560ce9db307532592047066eac0674190d Date: Thu, 14 Nov 2013 18:11:00 -0000 [thread overview] Message-ID: <20131114181124.11628.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch, master has been updated via 918229560ce9db307532592047066eac0674190d (commit) from 57460bcf82df9e5e335be84ecc9bdef33dddc934 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=918229560ce9db307532592047066eac0674190d commit 918229560ce9db307532592047066eac0674190d Author: Tom Tromey <tromey@redhat.com> Date: Thu Nov 14 11:09:14 2013 -0700 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. ----------------------------------------------------------------------- Summary of changes: gdb/ChangeLog | 5 +++++ gdb/python/py-linetable.c | 4 ++-- 2 files changed, 7 insertions(+), 2 deletions(-) hooks/post-receive -- gdb and binutils
reply other threads:[~2013-11-14 18:11 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20131114181124.11628.qmail@sourceware.org \ --to=tromey@sourceware.org \ --cc=src-cvs@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).