public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tmstaedt@t-mittelstaedt.de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/13869] New: Latest gdb 7.4 (CVS HEAD) has problem with "target async": Cannot get thread event message: debugger service failed
Date: Mon, 19 Mar 2012 21:07:00 -0000	[thread overview]
Message-ID: <bug-13869-4717@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 13869
           Summary: Latest gdb 7.4 (CVS HEAD) has problem with "target
                    async": Cannot get thread event message: debugger
                    service failed
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: threads
        AssignedTo: unassigned@sourceware.org
        ReportedBy: tmstaedt@t-mittelstaedt.de
    Classification: Unclassified


Just updated via cvs to the latest gdb 7.4 code and - as in a couple of
previous tries - gdb seems to have a problem when I run my custom build of
evolution 
in target async mode.

The following is in my .gdbinit:
set target-async 1
set non-stop on

Then I usually run it via gdb -x ../.gdbinit appname.

gdb hangs with the "Cannot get thread event message: debugger service failed"
message. gdb 7.3 has no problems with that.
I run an ubuntu linux, version 9.10 karmic, Linux linux1 2.6.31-23-generic
#75-Ubuntu SMP Fri Mar 18 18:08:39 UTC 2011 i686 GNU/Linux.

Without the above target-async, gdb starts the app okay.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-03-19 21:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 21:07 tmstaedt@t-mittelstaedt.de [this message]
2012-05-04  6:42 ` [Bug threads/13869] " aegges at web dot de
2012-05-23  7:29 ` qiyao at gcc dot gnu.org
2013-02-28 14:06 ` aegges at web dot de
2013-02-28 14:13 ` qiyao at gcc dot gnu.org
2013-02-28 14:15 ` qiyao at gcc dot gnu.org
2013-05-16 17:30 ` lionel at mamane dot lu
2013-07-20 21:57 ` camilocc at gmail dot com
2014-04-05  1:26 ` malaperle at gmail dot com

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-13869-4717@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).