public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17206] Assertion `pc_in_thread_step_range (pc, tp)' failed.
Date: Mon, 28 Jul 2014 06:19:00 -0000 [thread overview]
Message-ID: <bug-17206-4717-z6AdyFjnYh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17206-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17206
Yao Qi <qiyao at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |qiyao at gcc dot gnu.org
--- Comment #2 from Yao Qi <qiyao at gcc dot gnu.org> ---
The reproducer can be simpler,
$ cat 2.c
int
main(void)
{
return 0;
}
$ gcc 2.c -o 2.exe
(gdb) b main
Breakpoint 1 at 0x8048403
(gdb) run
Starting program: /home/yao/Source/gnu/gdb/build-git/2.exe
Breakpoint 1, 0x08048403 in main ()
(gdb) until
0x08048408 in main ()
(gdb) until
../../../git/gdb/infrun.c:1992: internal-error: resume: Assertion
`pc_in_thread_step_range (pc, tp)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
I have a patch which is being regression tested. I'll post it once the
regression test is finished.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-07-28 6:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 19:14 [Bug gdb/17206] New: " tilkax at gmail dot com
2014-07-27 19:18 ` [Bug gdb/17206] " xdje42 at gmail dot com
2014-07-28 6:19 ` qiyao at gcc dot gnu.org [this message]
2014-07-29 4:05 ` cvs-commit at gcc dot gnu.org
2014-07-29 6:36 ` cvs-commit at gcc dot gnu.org
2014-07-29 6:42 ` qiyao at gcc dot gnu.org
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-17206-4717-z6AdyFjnYh@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).