public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pedro at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/9817] GDB goes to 100% CPU usage indefinitely if pthread stack address is modified
Date: Wed, 04 Feb 2009 13:09:00 -0000 [thread overview]
Message-ID: <20090204130931.16766.qmail@sourceware.org> (raw)
In-Reply-To: <20090204120332.9817.mihai.stanescu@gmail.com>
------- Additional Comments From pedro at codesourcery dot com 2009-02-04 13:09 -------
Subject: Re: New: GDB goes to 100% CPU usage indefinitely if pthread stack address is modified
Hi,
On Wednesday 04 February 2009 12:03:33, mihai dot stanescu at gmail dot com wrote:
> The particular thing about the program is that is doing a pthread_attr_setstack
> to setup the thread stack to a dynamically allocated memory area on heap.
>
> pthread_attr_setstack(&attr, alignedStackBase, THREAD_STACK_SIZE -
> 2*PTHREAD_STACK_MIN)
>
Any chance you have a minimal test app you could attach that reproduce
the problem?
There have been numerous fixes since gdb 6.8. Could you please try
what happens with a recent gdb snapshot (or cvs head)?
Thanks,
--
http://sourceware.org/bugzilla/show_bug.cgi?id=9817
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2009-02-04 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 12:03 [Bug threads/9817] New: " mihai dot stanescu at gmail dot com
2009-02-04 12:05 ` [Bug threads/9817] " mihai dot stanescu at gmail dot com
2009-02-04 12:32 ` [Bug gdb/9817] " mihai dot stanescu at gmail dot com
2009-02-04 12:33 ` [Bug threads/9817] " mihai dot stanescu at gmail dot com
2009-02-04 13:09 ` pedro at codesourcery dot com [this message]
2009-02-05 10:32 ` mihai dot stanescu at gmail dot com
2009-02-05 11:18 ` mihai dot stanescu at gmail dot com
[not found] <bug-9817-4717@http.sourceware.org/bugzilla/>
2011-12-14 16:02 ` dje at google 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=20090204130931.16766.qmail@sourceware.org \
--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).