public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "saugustine at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/16168] New: Signal heavy execution + repeated breakpoint locks up gbserver
Date: Wed, 13 Nov 2013 20:28:00 -0000 [thread overview]
Message-ID: <bug-16168-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=16168
Bug ID: 16168
Summary: Signal heavy execution + repeated breakpoint locks up
gbserver
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: server
Assignee: unassigned at sourceware dot org
Reporter: saugustine at google dot com
Created attachment 7276
--> http://sourceware.org/bugzilla/attachment.cgi?id=7276&action=edit
files to reproduce.
The attached tar file includes a source file, a bash script, and a gdb script
which exposes a bug in gdbserver's signal handling.
You can simply run sh doit.sh to reproduce the problem.
gdbserver attaches to a multi-threaded application, which is also taking
SIGPROF signals.
The program repeatedly hits a breakpoint in some of the threads, and continues.
At some point, the SIGPROF will trigger a situation where a thread has a
pending signal, so gdbserver elects not to restart all threads.
In the included gdbserver.log file, this is the line: "Not resuming, all-stop
and found an LWP with pending status."
The only thread ever restarted is the pending one. Eventually, this thread runs
out of work and the system locks up.
There is a race involved, so you may need to run it a couple of times.
Sometimes it happens very early, and these are the easiest logs to study.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2013-11-13 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 20:28 saugustine at google dot com [this message]
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
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@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).