public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/16329] support for gdb's remote debugging broken on Solaris
Date: Mon, 16 Dec 2013 14:06:00 -0000	[thread overview]
Message-ID: <bug-16329-4717-jYuQ8nZO3g@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16329-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=16329

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
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  9a362b9a3291ef43316e1606e2b26fe55ebb187f (commit)
      from  4bc461905647a55faac8fe5eda16cc9f0266721d (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=9a362b9a3291ef43316e1606e2b26fe55ebb187f

commit 9a362b9a3291ef43316e1606e2b26fe55ebb187f
Author: Pedro Alves <palves@redhat.com>
Date:   Mon Dec 16 14:04:52 2013 +0000

    PR 16329: remote debugging broken on Solaris.

    Like on GNU/Linux (linux-thread-db.c), the Solaris solaris-threads
    target (handles libthread_db.so) shouldn't be pushed when remote
    debugging.

    This uses the same predicate used by linux-thread-db.c.

    gdb/
    2013-12-16  Pedro Alves  <palves@redhat.com>

        PR 16329
        * sol-thread.c (check_for_thread_db): If the target can't run or
        isn't a core, return without pushing.

-----------------------------------------------------------------------

Summary of changes:
 gdb/ChangeLog    |    6 ++++++
 gdb/sol-thread.c |    4 ++++
 2 files changed, 10 insertions(+), 0 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-12-16 14:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-14  3:31 [Bug remote/16329] New: " ivosh at ivosh dot net
2013-12-14  3:31 ` [Bug remote/16329] " ivosh at ivosh dot net
2013-12-14  4:18 ` ivosh at ivosh dot net
2013-12-16 14:06 ` cvs-commit at gcc dot gnu.org [this message]
2013-12-16 14:15 ` cvs-commit at gcc dot gnu.org
2013-12-16 14:33 ` palves at redhat dot com
2013-12-16 15:59 ` palves at redhat dot com
2014-01-27 17:48 ` cvs-commit at gcc dot gnu.org

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=bug-16329-4717-jYuQ8nZO3g@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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: link
Be 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).