public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tomi.kyostila at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/14443] New: Mach error in function darwin_resume_thread when continuing after attaching to a process
Date: Wed, 08 Aug 2012 09:34:00 -0000	[thread overview]
Message-ID: <bug-14443-4717@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 14443
           Summary: Mach error in function darwin_resume_thread when
                    continuing after attaching to a process
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
        AssignedTo: unassigned@sourceware.org
        ReportedBy: tomi.kyostila@gmail.com
    Classification: Unclassified


Steps to reproduce:

1. $ gdb
2. (gdb) attach 12688
3. (gdb) continue


Actual results:

Output:
Continuing.
warning: Mach error at "darwin-nat.c:726" in function "darwin_resume_thread":
(os/kern) failure (0x5)

The attached process continues to run normally, but gdb does not break on
Ctrl-C. When the attached process terminates, gdb returns to the (gdb) prompt.


Expected results:

gdb should break on Ctrl-C.


Running GNU gdb (GDB) 7.5.50.20120806-cvs (configured as
"x86_64-apple-darwin10.8.0") on Darwin iMac.local 10.8.0 Darwin Kernel Version
10.8.0: Tue Jun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386

-- 
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-08-08  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08  9:34 tomi.kyostila at gmail dot com [this message]
2013-01-16 22:31 ` [Bug gdb/14443] " thomas.fanghaenel at gmail dot com
2013-06-25 14:13 ` omar.awile 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-14443-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).