public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/16168] Signal heavy execution + repeated breakpoint locks up gbserver
Date: Wed, 04 Dec 2013 19:37:00 -0000 [thread overview]
Message-ID: <bug-16168-4717-m9YYLvQcJR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16168-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16168
--- Comment #3 from dje at google dot com ---
(In reply to dje from comment #2)
> What happens here is this:
For completeness sake, that's from analyzing the hang using thread-test-2 in
the attached testcase.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-12-04 19:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 20:28 [Bug server/16168] New: " saugustine at google dot com
2013-11-14 1:06 ` [Bug server/16168] " saugustine at google dot com
2013-12-04 19:36 ` dje at google dot com
2013-12-04 19:37 ` dje at google dot com [this message]
2014-11-23 15:05 ` eclipsehivernale at sfr dot fr
2014-11-23 15:33 ` eclipsehivernale at sfr dot fr
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-16168-4717-m9YYLvQcJR@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).