public inbox for archer-commits@sourceware.org help / color / mirror / Atom feed
From: jkratoch@sourceware.org To: archer-commits@sourceware.org Subject: [SCM] jankratochvil/gdbserverbuildid: Merge branch 'common-mergehex-empty-moveprep-move-attrgen-validate' into common-mergehex-empty-moveprep-move-attrgen-validate-tests Date: Wed, 26 Feb 2014 21:19:00 -0000 [thread overview] Message-ID: <20140226211929.14441.qmail@sourceware.org> (raw) The branch, jankratochvil/gdbserverbuildid has been updated via de59d31f0e7d694bf74a5bd539ae28a70c87daf1 (commit) via 114d2496eb0a546e45ba6231323f4726c7ad8f98 (commit) via c042536bf1cf98141bdfea27bbfc4879edb2ef6b (commit) via 02febadf5c8b484cdf4f6c21d180bb69806977e5 (commit) via 6e89496603071fcffee39778e90470507f921cc6 (commit) from 70d1332fddaf6a882bb29f71ca06c11c20c0142c (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email. - Log ----------------------------------------------------------------- commit de59d31f0e7d694bf74a5bd539ae28a70c87daf1 Merge: 70d1332 114d249 Author: Jan Kratochvil <jan.kratochvil@redhat.com> Date: Wed Feb 26 22:19:20 2014 +0100 Merge branch 'common-mergehex-empty-moveprep-move-attrgen-validate' into common-mergehex-empty-moveprep-move-attrgen-validate-tests commit 114d2496eb0a546e45ba6231323f4726c7ad8f98 Merge: c734bd1 c042536 Author: Jan Kratochvil <jan.kratochvil@redhat.com> Date: Wed Feb 26 22:19:20 2014 +0100 Merge branch 'common-mergehex-empty-moveprep-move-attrgen' into common-mergehex-empty-moveprep-move-attrgen-validate commit c042536bf1cf98141bdfea27bbfc4879edb2ef6b Merge: 616244b 02febad Author: Jan Kratochvil <jan.kratochvil@redhat.com> Date: Wed Feb 26 22:19:19 2014 +0100 Merge branch 'common-mergehex-empty-moveprep-move' into common-mergehex-empty-moveprep-move-attrgen commit 02febadf5c8b484cdf4f6c21d180bb69806977e5 Merge: bd75981 6e89496 Author: Jan Kratochvil <jan.kratochvil@redhat.com> Date: Wed Feb 26 22:19:19 2014 +0100 Merge branch 'common-mergehex-empty-moveprep' into common-mergehex-empty-moveprep-move commit 6e89496603071fcffee39778e90470507f921cc6 Author: Jan Kratochvil <jan.kratochvil@redhat.com> Date: Wed Feb 26 22:19:14 2014 +0100 . ----------------------------------------------------------------------- Summary of changes: gdb/linux-tdep.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) First 500 lines of diff: diff --git a/gdb/linux-tdep.c b/gdb/linux-tdep.c index 235a7c2..d0c8761 100644 --- a/gdb/linux-tdep.c +++ b/gdb/linux-tdep.c @@ -737,7 +737,7 @@ linux_find_memory_regions_gdb (struct gdbarch *gdbarch, /* We need to know the real target PID so linux_find_memory_regions_full can access /proc. */ if (current_inferior ()->fake_pid_p) - return 1; + return -1; cleanup = make_cleanup (free_current_contents, &memory_to_free); retval = linux_find_memory_regions_full (current_inferior ()->pid, hooks/post-receive -- Repository for Project Archer.
next reply other threads:[~2014-02-26 21:19 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-26 21:19 jkratoch [this message] -- strict thread matches above, loose matches on Subject: below -- 2014-02-27 20:19 jkratoch 2014-02-27 17:52 jkratoch 2014-02-26 21:39 jkratoch 2014-02-26 20:13 jkratoch 2014-02-26 19:52 jkratoch 2014-02-26 19:50 jkratoch
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=20140226211929.14441.qmail@sourceware.org \ --to=jkratoch@sourceware.org \ --cc=archer-commits@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).