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/18002] New: gdb/infrun.c:2114: internal-error: resume: Assertion `tp->control.step_resume_breakpoint->loc->permanent' failed. Date: Fri, 20 Feb 2015 12:14:00 -0000 [thread overview] Message-ID: <bug-18002-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=18002 Bug ID: 18002 Summary: gdb/infrun.c:2114: internal-error: resume: Assertion `tp->control.step_resume_breakpoint->loc->permanent' failed. Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: qiyao at gcc dot gnu.org I see the internal error below in gdb.base/bp-permanent.exp in aarch64-linux-gnu target. (gdb) PASS: gdb.base/bp-permanent.exp: always_inserted=off, sw_watchpoint=0: stepi signal with handler: stop at permanent breakpoint queue-signal SIGUSR1^M (gdb) PASS: gdb.base/bp-permanent.exp: always_inserted=off, sw_watchpoint=0: stepi signal with handler: queue-signal SIGUSR1 stepi^M gdb/infrun.c:2114: internal-error: resume: Assertion `tp->control.step_resume_breakpoint->loc->permanent' failed.^M A problem internal to GDB has been detected,^M further debugging may prove unreliable.^M Quit this debugging session? (y or n) FAIL: gdb.base/bp-permanent.exp: always_inserted=off, sw_watchpoint=0: stepi signal with handler: single-step to handler (GDB internal error) Resyncing due to internal error. Further analysis is needed. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2015-02-20 12:08 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-20 12:14 qiyao at gcc dot gnu.org [this message] 2015-02-20 12:41 ` [Bug gdb/18002] " qiyao at gcc dot gnu.org 2015-03-05 21:44 ` palves at redhat dot com 2015-03-05 23:41 ` palves at redhat dot com 2015-03-05 23:44 ` cvs-commit at gcc dot gnu.org 2015-03-06 15:29 ` palves at redhat 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-18002-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: linkBe 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).