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. 08c430507d34f825eaba019feb957de5bf876bad Date: Wed, 13 Nov 2013 17:05:00 -0000 [thread overview] Message-ID: <20131113170548.11132.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 08c430507d34f825eaba019feb957de5bf876bad (commit) from da0781dc5ffa0fdbec8d7fa65b053e3ef5a7997e (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=08c430507d34f825eaba019feb957de5bf876bad commit 08c430507d34f825eaba019feb957de5bf876bad Author: Tom Tromey <tromey@redhat.com> Date: Wed Nov 13 10:01:25 2013 -0700 fix multi-arch-exec for parallel mode I noticed today that multi-arch-exec.exp was failing in parallel mode. The bug is that multi-arch-exec.c assumes the non-parallel directory layout. This patch fixes the problem using the same "BASEDIR" approach used in other tests. Tested both ways on x86-64 Fedora 18. I'm checking this in. 2013-11-13 Tom Tromey <tromey@redhat.com> * gdb.multi/multi-arch-exec.exp: Define BASEDIR when compiling. * gdb.multi/multi-arch-exec.c (main): Use BASEDIR. ----------------------------------------------------------------------- Summary of changes: gdb/testsuite/ChangeLog | 5 +++++ gdb/testsuite/gdb.multi/multi-arch-exec.c | 4 ++-- gdb/testsuite/gdb.multi/multi-arch-exec.exp | 5 ++++- 3 files changed, 11 insertions(+), 3 deletions(-) hooks/post-receive -- gdb and binutils
reply other threads:[~2013-11-13 17:05 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=20131113170548.11132.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).