public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "fyzmat at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/12709] Stepping on a while loop freezes the GDB (MIPS platform)
Date: Wed, 27 Apr 2011 20:38:00 -0000 [thread overview]
Message-ID: <bug-12709-4717-jdkkBJvhQ1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12709-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12709
fyzmat at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
Severity|normal |enhancement
--- Comment #2 from fyzmat at gmail dot com 2011-04-27 20:38:28 UTC ---
Thanks for the answer,
I can understand, that the described behaviour is correct.
When I try to reproduce this in standart C desktop application, the GDB will
stop on the while line after the step command. So I considered the behaviour
bad.
The 'c' variable can be changed for example from another thread. From my point
of view this behaviour can be little uncomfortable for the programmer, because
when applying the step command the GDB will be frozen until the 'c' is changed.
This can take very long, because the GDB is just single stepping for all the
time. (In my case it takes minutes). Thus the programmer is forced to restart
the debugging session.
I will reopen the bug, because I am not sure, if anybody would notice the
resolved bug.
Tomas
--
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.
next prev parent reply other threads:[~2011-04-27 20:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 19:17 [Bug gdb/12709] New: " fyzmat at gmail dot com
2011-04-27 19:51 ` [Bug gdb/12709] " pedro at codesourcery dot com
2011-04-27 20:38 ` fyzmat at gmail dot com [this message]
2011-04-27 21:27 ` pedro at codesourcery dot com
2011-04-28 9:04 ` fyzmat at gmail dot com
2011-04-28 12:26 ` pedro at codesourcery dot com
2011-04-28 21:46 ` fyzmat at gmail dot com
2011-04-28 21:47 ` fyzmat at gmail dot com
2011-04-28 21:57 ` fyzmat at gmail dot com
2011-04-28 21:58 ` fyzmat at gmail dot com
2011-04-29 10:03 ` pedro at codesourcery 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-12709-4717-jdkkBJvhQ1@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).